Bug#782336: okular: Cannot print from okular
Package: okular Version: 4:23.08.1-2+b1 Followup-For: Bug #782336 Dear Maintainer, I'm observing the same behavior. In my specific case, I was trying to print a range of pages from a PDF. Instead, an `lpr` usage message appeared on the terminal: ``` usage: lpr [-cdfghlmnpqrstv] [-#num] [-1234 font] [-C class] [-i [numcols]] [-J job] [-Pprinter] [-T title] [-U user] [-wnum] [name ...] ``` `okular` itself reports no error or any other indication that the print operation failed. It's not listed in the dependencies below, but I also have installed: * cups v2.4.7-1.1+b1 * lpr 1:2008.05.17.3+nmu2 Schwab -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.7.12-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_FIRMWARE_WORKAROUND Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages okular depends on: ii kinit 5.115.0-2 ii kio 5.115.0-6 ii libc6 2.38-11 ii libfreetype62.13.2+dfsg-1+b4 ii libjpeg62-turbo 1:2.1.5-3 ii libkf5activities5 5.115.0-3 ii libkf5archive5 5.115.0-2 ii libkf5bookmarks55.115.0-2 ii libkf5codecs5 5.115.0-2 ii libkf5completion5 5.115.0-2 ii libkf5configcore5 5.115.0-2 ii libkf5configgui55.115.0-2 ii libkf5configwidgets55.115.0-2 ii libkf5coreaddons5 5.115.0-2 ii libkf5crash55.115.0-2 ii libkf5i18n5 5.115.1-2 ii libkf5itemviews55.115.0-2 ii libkf5jobwidgets5 5.115.0-2 ii libkf5kexiv2-15.0.0 23.04.2-2+b1 ii libkf5kiocore5 5.115.0-6 ii libkf5kiogui5 5.115.0-6 ii libkf5kiowidgets5 5.115.0-6 ii libkf5parts55.115.0-2 ii libkf5pty5 5.115.0-2 ii libkf5purpose-bin 5.115.0-2 ii libkf5purpose5 5.115.0-2 ii libkf5textwidgets5 5.115.0-2 ii libkf5wallet-bin5.115.0-2 ii libkf5wallet5 5.115.0-2 ii libkf5widgetsaddons55.115.0-2 ii libkf5windowsystem5 5.115.0-2 ii libkf5xmlgui5 5.115.0-2 ii libokular5core114:23.08.1-2+b1 ii libphonon4qt5-4t64 4:4.12.0-3.1+b1 ii libpoppler-qt5-1t64 24.02.0-5 ii libqmobipocket2 4:22.12.3-1+b2 ii libqt5core5t64 5.15.10+dfsg-7.2+b1 ii libqt5dbus5t64 5.15.10+dfsg-7.2+b1 ii libqt5gui5t64 5.15.10+dfsg-7.2+b1 ii libqt5printsupport5t64 5.15.10+dfsg-7.2+b1 ii libqt5texttospeech5 5.15.10-2+b2 ii libqt5widgets5t64 5.15.10+dfsg-7.2+b1 ii libqt5x11extras55.15.10-2+b2 ii libqt5xml5t64 5.15.10+dfsg-7.2+b1 ii libspectre1 0.2.12-1+b1 ii libstdc++6 14.1.0-1 ii phonon4qt5 4:4.12.0-3.1+b1 ii zlib1g 1:1.3.dfsg+really1.3.1-1 Versions of packages okular recommends: pn cups-bsd Versions of packages okular suggests: ii ghostscript10.03.1~dfsg~git20240518-1 pn okular-extra-backends ii poppler-data 0.4.12-1 ii texlive-binaries 2023.20230311.66589-9+b2 ii unrar 1:7.0.9-1 -- no debconf information
Bug#1070236: python3-samba: SyntaxError during configuration phase of package on upgrade
Did you fix this one, too? --- Performing actions... Setting up python3-samba (2:4.19.6+dfsg-2) ... File "/usr/lib/python3/dist-packages/samba/ms_schema_markdown.py", line 25 try ^ SyntaxError: expected ':' File "/usr/lib/python3/dist-packages/samba/ms_schema_markdown.py", line 25 try ^ SyntaxError: expected ':' dpkg: error processing package python3-samba (--configure): --- Schwab
Bug#1069591: cyckle: Fails to start
This BUG was fixed in cycle 0.3.3. Please upgrade to https://debian.pkgs.org/sid/debian-main-arm64/cycle_0.3.3-1_all.deb.html
Bug#1063191: libcifpp-data: Incorrect URL in update-libcifpp-data script
Hi Andreas, The URL's were updated in upstream some time ago. The debian version of libcifpp (and all dependent tools) are a bit out of date. The problem I have is that development of libcifpp is a bit too fast. Whenever I break the ABI I have to ask for someone to upload a newer version. And last time this apparently did not went well and so the update stalled. I don't remember who I asked to update, but since that didn't happen I forgot about it. Anyway, so I had an upload ready for version 5.2 and libcifpp is now at version 6.1. I will thus have to prepare yet another update and then upload all depending packages. I'll see what I can do. regards, -maarten Op 13-02-2024 om 08:28 schreef Andreas Tille: Hi Maarten, since last September there is a new upstream version in Git which was not uploaded. I see less instances of ftp.wwpdb.org in this code but there are some remainings. It would be great if you could upload your preparation after checking that the bug below is fixed. Kind regards Andreas. Am Mon, Feb 05, 2024 at 11:27:36AM -0500 schrieb Rick Bernard: Package: libcifpp-data Version: 5.0.7.1-3 Severity: important Tags: patch Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installing libcifpp-data via "apt install". The incorrect URL causes apt to hang for a long period of time before returrning to a prompt. As a result, the file supposed to be loaced in /var/cache/libcifpp/components.cif fails to download. The Stable version of this package was showing timeout errors when attempting to connect to https://ftp.wwpdb.org. The correct URL that is published by wwpdb.org is https://files.wwpdb.org for downloading via HTTP. This will happen durring install via apt when you are prompted Package configuration about setting up weekly downloads of these data files from wwpdb.org. * What exactly did you do (or not do) that was effective (or ineffective)? Editing the file /etc/cron.weekly/update-libcifpp-data and changing the URL for the components.cif download from https://ftp.wwpdb.org to https://files.wwpdb.org leaving all subpaths the same resolves the issue. This also helps with the stable version of this package and fixes dpkg and apt when running "dpkg --configure -a" * What was the outcome of this action? Resolves the package install and fixes apt/dpkg package management system. * What outcome did you expect instead? The expected outcome is that "apt install" will successfully install the package and be able to run the download scripts successfully. *** End of the template - remove these template lines *** -- System Information: Debian Release: 12.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-17-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcifpp-data depends on: ii debconf [debconf-2.0] 1.5.82 libcifpp-data recommends no packages. libcifpp-data suggests no packages. -- debconf information: * libcifpp/update: true --- update-libcifpp-data.orig 2024-02-05 11:13:15.964579981 -0500 +++ update-libcifpp-data2024-02-05 11:24:35.219320601 -0500 @@ -60,7 +60,7 @@ # Update the dictionaries -update_dictionary "/var/cache/libcifpp/components.cif" "https://ftp.wwpdb.org/pub/pdb/data/monomers/components.cif.gz; +update_dictionary "/var/cache/libcifpp/components.cif" "https://files.wwpdb.org/pub/pdb/data/monomers/components.cif.gz; update_dictionary "/var/cache/libcifpp/mmcif_pdbx.dic" "https://mmcif.wwpdb.org/dictionaries/ascii/mmcif_pdbx_v50.dic.gz; update_dictionary "/var/cache/libcifpp/mmcif_ma.dic" "https://github.com/ihmwg/ModelCIF/raw/master/dist/mmcif_ma.dic; ___ Debian-med-packaging mailing list debian-med-packag...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- Maarten L. Hekkelman http://www.hekkelman.com/
Bug#1061409: rasdaemon does not actually support PAGE_CE_ACTION etc.
Package: rasdaemon Version: 0.6.8-1.1 rasdaemon upstream offers the ability to offline memory when failures are detected (see <https://github.com/mchehab/rasdaemon/commit/9ae6b70eff>). Debian's rasdaemon includes the configuration files to do that at /etc/default/rasdaemon, with lines like: PAGE_CE_REFRESH_CYCLE="24h" PAGE_CE_THRESHOLD="50" PAGE_CE_ACTION="soft" This makes it look like the feature is enabled. However, those settings in /etc/default/rasdaemon are never actually used, and rasdaemon will never try to offline failing memory, because the Debian package is not compiled with the necessary "--enable-memory-ce-pfa" flag. Compiling rasdaemon with "--enable-memory-ce-pfa" would fix this. I tested compiling with that extra flag, and if you do so, these new lines are emitted in the logs when it is started, indicating the code is working: rasdaemon: Page offline choice on Corrected Errors is soft rasdaemon: Threshold of memory Corrected Errors is 50 / 24h I'd like to suggest that this option be enabled. If people don't want to use this feature, they can edit /etc/default/rasdaemon as documented to change it to PAGE_CE_ACTION="off". If it is decided not to enable this feature, then /etc/default/rasdaemon should be modified to remove these options so it doesn't look like it is enabled. -- Robert L Mathews
Bug#1060308: hcloud-cli version is not set
Package: hcloud-cli Version: 1.30.3-1+b5 Severity: normal Dear Maintainer, The hcloud-cli distributed by debian does not have its version set. This leads to 2 problems: - the 'hcloud version' command does not return the expected version info: expected output: hcloud 1.41.1 current output: hcloud was not built properly - the user agent used to call the Hetzner Cloud API does not include the version: expected user agent: hcloud-cli/v1.41.1 hcloud-go/2.5.1 current user againt: hcloud-cli/was not built properly hcloud-go/2.5.1 The way the version is handled upstream has recently changed, and it should mitigate part of this issue: https://github.com/hetznercloud/cli/commit/af9dec448dfaf5331d5200d96722e5c648c25624#diff-8aa632a6f4ad2a3a7fef52661816aa3977f23c0673ef29633c01116fee6745c6 To fully solve this issue, I suggest that the debian build process updates the relevant version variables using the linker flags, as we currenlty do in the upstream build process: https://github.com/hetznercloud/cli/blob/e1bd800db671e9deb68a86bd5ff810211f56a7d5/.goreleaser.yml#L11-L12 The linker flags below could be used in the debian package build command: # Set the version to the debian version (maybe adding a local debian build number?) -X github.com/hetznercloud/cli/internal/version.version="$(DEB_VERSION_UPSTREAM)+debian.1" # Remove the -dev suffix, this is not a dev/pre relesease -X github.com/hetznercloud/cli/internal/version.versionPrerelease="" Thanks for considering this bug. Cheers, Jonas -- System Information: Debian Release: 12.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-17-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages hcloud-cli depends on: ii libc6 2.36-9+deb12u3 hcloud-cli recommends no packages. hcloud-cli suggests no packages. -- no debconf information
Bug#1055626: cabal-install: pkg-config package gtk4-any, not found in the pkg-config database
Package: cabal-install Version: 3.8.1.0-1 Severity: normal Dear Maintainer, When I try to install gi-gtk-4.0.8 I get the following error ``` Resolving dependencies... Error: cabal: Could not resolve dependencies: [__0] next goal: gi-gtk (user goal) [__0] rejecting: gi-gtk-4.0.8 (conflict: pkg-config package gtk4-any, not found in the pkg-config database) [__0] rejecting: gi-gtk-4.0.6, gi-gtk-4.0.5, gi-gtk-4.0.4, gi-gtk-4.0.3, gi-gtk-4.0.2, gi-gtk-4.0.1, gi-gtk-3.0.41, gi-gtk-3.0.39, gi-gtk-3.0.38, gi-gtk-3.0.37, gi-gtk-3.0.36, gi-gtk-3.0.35, gi-gtk-3.0.34, gi-gtk-3.0.33, gi-gtk-3.0.32, gi-gtk-3.0.31, gi-gtk-3.0.30, gi-gtk-3.0.29, gi-gtk-3.0.28, gi-gtk-3.0.27, gi-gtk-3.0.26, gi-gtk-3.0.25, gi-gtk-3.0.24, gi-gtk-3.0.23, gi-gtk-3.0.22, gi-gtk-3.0.21, gi-gtk-3.0.20, gi-gtk-3.0.19, gi-gtk-3.0.18, gi-gtk-3.0.17, gi-gtk-3.0.16, gi-gtk-3.0.15, gi-gtk-3.0.14, gi-gtk-3.0.13, gi-gtk-3.0.12, gi-gtk-3.0.11, gi-gtk-3.0.10, gi-gtk-3.0.9, gi-gtk-3.0.8, gi-gtk-3.0.7, gi-gtk-3.0.6, gi-gtk-3.0.5, gi-gtk-3.0.4, gi-gtk-3.0.3, gi-gtk-3.0.2, gi-gtk-3.0.1, gi-gtk-0.3.18.15, gi-gtk-0.3.18.14, gi-gtk-0.3.18.13, gi-gtk-0.3.18.12, gi-gtk-0.3.16.12, gi-gtk-0.3.18.10, gi-gtk-0.3.16.11, gi-gtk-0.3.16.10, gi-gtk-0.3.16.9, gi-gtk-0.3.16.8 (constraint from user target requires ==4.0.8) [__0] fail (backjumping, conflict set: gi-gtk) After searching the rest of the dependency tree exhaustively, these were the goals I've had most trouble fulfilling: gi-gtk ``` Apt says that `libgtk-4-dev is already the newest version (4.12.3+ds-2)`. -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cabal-install depends on: ii ghc 9.4.7-1 ii libc6 2.37-12 ii libffi8 3.4.4-1 ii libgmp10 2:6.3.0+dfsg-2 ii zlib1g1:1.2.13.dfsg-3 Versions of packages cabal-install recommends: ii curl 8.4.0-2 ii wget 1.21.4-1+b1 cabal-install suggests no packages. -- no debconf information
Bug#1055061: openems: New version available
Package: openems Version: 0.0.35+git20190103.6a75e98+dfsg.1-3.2 Severity: normal Dear Maintainer, a new version of openEMS is available (0.0.36) with significant fixes and improvements. Please update the package. Thank you. -- System Information: Debian Release: trixie/sid merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-3-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US: Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages openems depends on: ii libc6 2.37-12 ii libcsxcad0 0.0.35+git20190103.6a75e98+dfsg.1-3.2 ii libcurl4 8.4.0-2 ii libdouble-conversion3 3.3.0-1 ii libexpat1 2.5.0-2 ii libfreetype6 2.13.2+dfsg-1 ii libgcc-s1 13.2.0-6 ii libgl2ps1.41.4.2+dfsg1-2 ii libglew2.2 2.2.0-4+b1 ii libglx01.7.0-1 ii libhdf5-103-1 1.10.10+repack-3 ii libhdf5-hl-100 1.10.10+repack-3 ii libicu72 72.1-4 ii libjpeg62-turbo1:2.1.5-2 ii libjsoncpp25 1.9.5-6 ii liblz4-1 1.9.4-1 ii liblzma5 5.4.4-0.1 ii libnetcdf191:4.9.2-2 ii libnf2ff0 0.0.35+git20190103.6a75e98+dfsg.1-3.2 ii libogg01.3.5-3 ii libopenems00.0.35+git20190103.6a75e98+dfsg.1-3.2 ii libopengl0 1.7.0-1 ii libopenmpi34.1.6-1 ii libpng16-161.6.40-2 ii libproj25 9.3.0-1 ii libpython3.11 3.11.6-3 ii libqcsxcad00.0.35+git20190103.6a75e98+dfsg.1-3.2 ii libqt5core5a 5.15.10+dfsg-4 ii libqt5gui5 5.15.10+dfsg-4 ii libqt5opengl5 5.15.10+dfsg-4 ii libqt5widgets5 5.15.10+dfsg-4 ii libqt5xml5 5.15.10+dfsg-4 ii libsqlite3-0 3.43.2-1 ii libssl33.0.12-1 ii libstdc++6 13.2.0-6 ii libsz2 1.1.2-1 ii libtbb12 2021.9.0-2 ii libtheora0 1.1.1+dfsg.1-16.1+b1 ii libtiff6 4.5.1+git230720-1 ii libvtk9.1 9.1.0+really9.1.0+dfsg2-7 ii libvtk9.1-qt 9.1.0+really9.1.0+dfsg2-7 ii libx11-6 2:1.8.7-1 ii libxml22.9.14+dfsg-1.3 ii zlib1g 1:1.2.13.dfsg-3 Versions of packages openems recommends: ii octave-openems 0.0.35+git20190103.6a75e98+dfsg.1-3.2 openems suggests no packages. -- no debconf information
Bug#1053223: python3-ipython: Interactive embedding of ipython using the InteractiveShellEmbed method as documented, is broken
Package: python3-ipython Version: 8.14.0-1 Severity: normal X-Debbugs-Cc: lgp171...@gmail.com Dear Maintainer, The IPython documentation has the following example on embedding it. https://github.com/ipython/ipython/blob/8.14.0/examples/Embedding/embed_class_long.py This example does not work with the python3-ipython package version 8.14.0-1 in Debian unstable and throws an exception. Here is a minimal example `ise.py` file which can reproduce this issue. ``` from IPython.terminal.embed import InteractiveShellEmbed ipshell = InteractiveShellEmbed() ipshell() ``` On running this script with `python3 ise.py`, it opens the IPython interactive shell. Typing any statements and pressing enter to execute it, causes an exception. Below is an instance of this error happening. ``` guruprasad@debian-sid:~$ python3 ise.py Python 3.11.5 (main, Aug 29 2023, 15:31:31) [GCC 13.2.0] Type 'copyright', 'credits' or 'license' for more information IPython 8.14.0 -- An enhanced Interactive Python. Type '?' for help. Unhandled exception in event loop: File "/usr/lib/python3.11/asyncio/events.py", line 80, in _run self._context.run(self._callback, *self._args) File "/usr/lib/python3/dist-packages/prompt_toolkit/input/vt100.py", line 162, in callback_wrapper callback() File "/usr/lib/python3/dist-packages/prompt_toolkit/application/application.py", line 712, in read_from_input_in_context context.copy().run(read_from_input) File "/usr/lib/python3/dist-packages/prompt_toolkit/application/application.py", line 692, in read_from_input self.key_processor.process_keys() File "/usr/lib/python3/dist-packages/prompt_toolkit/key_binding/key_processor.py", line 272, in process_keys self._process_coroutine.send(key_press) File "/usr/lib/python3/dist-packages/prompt_toolkit/key_binding/key_processor.py", line 187, in _process self._call_handler(matches[-1], key_sequence=buffer[:]) File "/usr/lib/python3/dist-packages/prompt_toolkit/key_binding/key_processor.py", line 322, in _call_handler handler.call(event) File "/usr/lib/python3/dist-packages/prompt_toolkit/key_binding/key_bindings.py", line 124, in call result = self.handler(event) ^^^ File "/usr/lib/python3/dist-packages/IPython/terminal/shortcuts/__init__.py", line 405, in handle_return_or_newline_or_execute return newline_or_execute_outer(shell)(event) ^^ File "/usr/lib/python3/dist-packages/IPython/terminal/shortcuts/__init__.py", line 428, in newline_or_execute status, indent = shell.check_complete(check_text) Exception 'NoneType' object has no attribute 'check_complete' Press ENTER to continue... ``` This breaks all the usages of the interactive shell embedding using the documented method. -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-1-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_IN.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-ipython depends on: ii python33.11.4-5+b1 ii python3-backcall 0.2.0-4 ii python3-decorator 5.1.1-5 ii python3-jedi 0.18.2-1 ii python3-matplotlib-inline 0.1.6-2 ii python3-pexpect4.8.0-4 ii python3-pickleshare0.7.5-5 ii python3-prompt-toolkit 3.0.39-2 ii python3-pygments 2.15.1+dfsg-1 ii python3-setuptools 68.1.2-1 ii python3-stack-data 0.6.2-3 ii python3-traitlets 5.5.0-2 python3-ipython recommends no packages. Versions of packages python3-ipython suggests: pn python-ipython-doc -- no debconf information
Bug#1052238: [pkg-php-pear] Bug#1052238: php-net-smtp: Please, consider this email address
I'm sorry, My code and the example from https://pear.php.net/manual/en/package.mail.mail-mime.example.php, both use the statement: $mail =Mail::factory('mail'); this statement forced the use of the mail driver based on the php intrinsic function mail() and is this function the one who has the bug I reported. Changing this statement to: $mail =Mail::factory('smtp'); the smtp driver based on php-net-smtp is used and its behavior is correct. Conclusion: the php-net-smtp package works fine and the bug might be closed. Thansk very much for your attention and I regret the inconveniences. On 21/9/23 14:57, Guilhem Moulin wrote: On Thu, 21 Sep 2023 at 13:58:18 +0200, J.L. Fernandez Jambrina wrote: Unfortunatelly I don't know how to use setDebug() to see what's is being passed to send() Please see https://github.com/pear/Net_SMTP#debugging to debug Net_SMTP. but I used two calls to var_dump() to see it: AFAICT this show what's being passed to Mail_Mime or Mail, not Net_SMTP. Net_SMTP treats data as as opaque string containing both the header and body parts, just like the SMTP protocol itself.
Bug#1052491: openems: AppCSXCAD not starting
Package: openems Version: 0.0.35+git20190103.6a75e98+dfsg.1-3.2 Severity: important Dear Maintainer, AppCSXCAD does not start and fails with the following message: AppCSXCAD: error while loading shared libraries: libjawt.so: cannot open shared object file: No such file or directory furthermore, examining with ldd shows: libjawt.so => not found libjvm.so => not found I don't know why such libraries should be needed to run AppCSXCAD, anyway Best regards, G.L.G. -- System Information: Debian Release: trixie/sid merged-usr: no Architecture: amd64 (x86_64) Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US: Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages openems depends on: ii libc6 2.37-10 ii libcsxcad0 0.0.35+git20190103.6a75e98+dfsg.1-3.2 ii libcurl4 8.3.0-1 ii libdouble-conversion3 3.3.0-1 ii libexpat1 2.5.0-2 ii libfreetype6 2.13.2+dfsg-1 ii libgcc-s1 13.2.0-4 ii libgl2ps1.41.4.2+dfsg1-2 ii libglew2.2 2.2.0-4+b1 ii libglx01.6.0-1 ii libhdf5-103-1 1.10.10+repack-2 ii libhdf5-hl-100 1.10.10+repack-2 ii libicu72 72.1-3 ii libjpeg62-turbo1:2.1.5-2 ii libjsoncpp25 1.9.5-6 ii liblz4-1 1.9.4-1 ii liblzma5 5.4.4-0.1 ii libnetcdf191:4.9.2-2 ii libnf2ff0 0.0.35+git20190103.6a75e98+dfsg.1-3.2 ii libogg01.3.5-3 ii libopenems00.0.35+git20190103.6a75e98+dfsg.1-3.2 ii libopengl0 1.6.0-1 ii libopenmpi34.1.5-3 ii libpng16-161.6.40-1 ii libproj25 9.3.0-1 ii libpython3.11 3.11.5-3 ii libqcsxcad00.0.35+git20190103.6a75e98+dfsg.1-3.2 ii libqt5core5a 5.15.10+dfsg-3 ii libqt5gui5 5.15.10+dfsg-3 ii libqt5opengl5 5.15.10+dfsg-3 ii libqt5widgets5 5.15.10+dfsg-3 ii libqt5xml5 5.15.10+dfsg-3 ii libsqlite3-0 3.43.1-1 ii libssl33.0.11-1 ii libstdc++6 13.2.0-4 ii libsz2 1.0.6-1+b1 ii libtbb12 2021.9.0-2 ii libtheora0 1.1.1+dfsg.1-16.1+b1 ii libtiff6 4.5.1+git230720-1 ii libvtk9.1 9.1.0+really9.1.0+dfsg2-7 ii libvtk9.1-qt 9.1.0+really9.1.0+dfsg2-7 ii libx11-6 2:1.8.6-1 ii libxml22.9.14+dfsg-1.3 ii zlib1g 1:1.2.13.dfsg-3 Versions of packages openems recommends: ii octave-openems 0.0.35+git20190103.6a75e98+dfsg.1-3.2 openems suggests no packages. -- no debconf information
Bug#1051328: Furthermore the script fails
I can confirm this bug. Furthermore the script fails with: /usr/sbin/grub-mkconfig: 300: /etc/grub.d/25_bli: not found I think this is because there no path in the script and "insmod bli" fails to find bli.mod. At this point grub.cfg is interrupted. GLG
Bug#1050949: Acknowledgement (routine-update had my rules for lunch)
I'm sorry, I messed up. This report should not have been sent. I used a wrong version of routine-update. -maarten Op 31-08-2023 om 19:33 schreef Debian Bug Tracking System: Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1050949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050949. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): Debian Med Packaging Team If you wish to submit further information on this problem, please send it to 1050...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system. -- Maarten L. Hekkelman http://www.hekkelman.com/
Bug#1050949: routine-update had my rules for lunch
Package: routine-update Severity: important Dear Maintainer, For my debian package I used the wiki page on SphinxDocumentation as inspiration and added the following lines to my rules file: override_dh_auto_build: export http_proxy=127.0.0.1:9 override_dh_auto_build: export https_proxy=127.0.0.1:9 override_dh_auto_build: dh_auto_build The reason to do this is that I wanted to have the http_proxy set while still running the regular build (using cmake). My cmake setup builds the documentation and this avoids sphinx to try to fetch resources from the internet. However, running routine-update on this package removed the last two lines and the effect was that nothing was built anymore. Of course, the rules file is suboptimal, but simply removing the last two lines makes it worse. regards, -maarten -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable-proposed-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-21-amd64 (SMP w/2 CPU threads) Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1042414: gitlab: Sidekiq not working after 16 upgrade
Package: gitlab Version: 16.0.7+ds1-3~fto12+2 Severity: important X-Debbugs-Cc: er_ma...@darkbolt.net Dear Maintainer, Hi, After updating gitlab 15.7 to 16.0, sidekiq is not starting, not allowing apt installation to end correctly. On the same moment I've do a release change from old stable. On sidekiq log file I can find this: /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/definition.rb:36:in `build': /etc/Gemfile not found (Bundler::GemfileNotFound) from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler.rb:208:in `definition' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler.rb:156:in `setup' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/setup.rb:20:in `block in ' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/ui/shell.rb:136:in `with_level' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/ui/shell.rb:88:in `silence' from /usr/share/rubygems-integration/all/gems/bundler-2.3.15/lib/bundler/setup.rb:20:in `' from :85:in `require' from :85:in `require' from /usr/share/gitlab/config/bundler_setup.rb:24:in `' from /usr/share/gitlab/sidekiq_cluster/cli.rb:3:in `require_relative' from /usr/share/gitlab/sidekiq_cluster/cli.rb:3:in `' from /usr/share/gitlab/bin/sidekiq-cluster:4:in `require_relative' from /usr/share/gitlab/bin/sidekiq-cluster:4:in `' Package gitlab-apt-pin-preferences are installed on the latest version before doing the apt-get upgrade and apt-get install gitlab. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable'), (100, 'bookworm-fasttrack'), (100, 'bookworm-backports-staging') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-16-amd64 (SMP w/8 CPU threads) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gitlab depends on: ii asciidoctor 2.0.18-2 ii bc 1.07.1-3+b1 ii bundler 2.3.15-2 ii bzip2 1.0.8-5+b1 ii dbconfig-pgsql 2.0.24 ii debconf [debconf-2.0] 1.5.82 ii exim4-daemon-light [mail-transport-age 4.96-15+deb12u1 nt] ii fonts-font-awesome [node-font-awesome] 5.0.10+really4.7.0~dfsg-4.1 ii gitlab-common 16.0.7+ds1-2~bpo12+1 ii gitlab-workhorse16.0.7+ds1-3~fto12+2 ii katex [node-katex] 0.16.4+~cs6.1.0-1 ii libjs-bootstrap4 [node-bootstrap] 4.6.1+dfsg1-4 ii libjs-pdf [node-pdfjs-dist] 2.14.305+dfsg-2 ii libjs-popper.js [node-popper.js]1.16.1+ds-6 ii libruby3.1 [ruby-rexml] 3.1.2-7 ii libssl-dev 3.0.9-1 ii lsb-base11.6 ii nginx [httpd] 1.22.1-9 ii node-autosize 4.0.4~dfsg1+~4.0.0-2 ii node-axios 1.2.1+dfsg-1 ii node-babel-loader 9.1.0-3 ii node-babel-plugin-lodash3.3.4+~cs2.0.1-6 ii node-babel7 7.20.15+ds1+~cs214.269.168-3 ii node-brace-expansion2.0.1-2 ii node-cache-loader 4.1.0+~cs2.0.0-4 ii node-clipboard 2.0.11+ds+~cs9.6.11-1 ii node-compression-webpack-plugin 10.0.0-2 ii node-copy-webpack-plugin11.0.0-3 ii node-core-js3.26.1-3 ii node-core-js-compat 3.26.1-3 ii node-core-js-pure 3.26.1-3 ii node-cron-validator 1.3.1-3 ii node-css-loader 6.7.2+~cs14.0.11-1 ii node-d3 5.16.0-10 ii node-d3-selection 1.4.0-8 ii node-dateformat 5.0.3-5 ii node-dompurify 2.4.1+dfsg+~2.4.0-1 ii node-exports-loader 4.0.0-1 ii node-file-loader6.2.0-3 ii node-fuzzaldrin-plus0.6.0+dfsg+~0.6.2-3 ii node-glob 8.0.3+~cs8.4.15-1 ii node-imports-loader 0.8.0-6 ii node-jed1.1.1-4 ii node-jquery 3.6.1+dfsg+~3.5.14-1 ii node-jquery-ujs 1.2.3-2 ii node-js-cookie 3.0.1+~3.0.0-3 ii node-js-yaml4.1.0+dfsg+~4.0.5-7 ii node-jszip 3.10.1+dfsg-1 ii node-jszip-utils0.1.0+dfsg-1 ii
Bug#1039508: systemd-boot: UEFI ZFS boot "Error preparing initrd: Bad Buffer Size"
Package: systemd-boot Severity: important Dear Maintainer, * I [fresh-] installed the latest version of Proxmox VE (8.0), which is based on Debian 12. * First boot after installation resulted in the error "Error preparing initrd: Bad Buffer Size" at boot, preventing system from loading. * I expected the system to boot normally. I was asked by the bugzilla folks at Proxmox to report this problem to you, as it is an issue with the current systemd-boot package. (I have omitted reportbug system information, as the reporting system is *not* the system on which the issue occurs.) -- Original report to Proxmox bugzilla: https://bugzilla.proxmox.com/show_bug.cgi?id=4798 Environment: - Dell r620 (x2) - 2x Xeon E5-2620 (each) - 64GB RAM (each) - BIOS 2.9.0 (dated 2020-02) - UEFI boot - PERC h310 SAS controller (IT mode) - PVE installed on 2x Dell/Seagate 15k SAS drives in ZFS mirror - Install media 8.0-2 ISO The first boot after a new install results in an "Error preparing initrd: Bad Buffer Size" error on both mentioned hosts. Previously, PVE v7.4 installed, booted, and ran fine on this hardware - I'd begun migration to Proxmox (v7) for virtual hosting last week, but started over once v8 was released. This Proxmox forum thread mentions the error occurring for others: https://forum.proxmox.com/threads/error-preparing-initrd-bad-buffer-size.129427/ And this github issue thread identifies the cause as systemd, and reports a merged patch which corrects it: https://github.com/systemd/systemd/issues/25911 Is there any chance to include a more recent version of systemd (the "-boot" or "-boot-efi" packages, I assume) with the install media? Or a recommended way to load a newer package version during install, prior to first boot? A possible workaround is to install 7.4 then immediately upgrade to 8; I have not yet attempted this. More context: https://github.com/NixOS/nixpkgs/issues/227431#issuecomment-1556474041 -- End original report Obviously, the report text is specific to Proxmox, but the issue lies with the current implemenation of systemd-boot. Please consider implementing the patch at https://github.com/systemd/systemd/commit/f70f992273a7add1ec98a894ffadb1f1e43c0c31 Thank you.
Bug#1038409: linux-image-6.3.0-1-amd64: CONFIG_RTW88_8822BU is disabled, preventing me from using my wifi adapter
Package: src:linux Version: 6.3.7-1 Severity: normal -- Package-specific info: ** Version: Linux version 6.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.3.7-1 (2023-06-12) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-9-amd64 root=UUID=86f5cc6e-383a-49be-bfed-4c37762c059d ro initrd=/install/gtk/initrd.gz quiet ** Tainted: POE (12289) * proprietary module was loaded * externally-built ("out-of-tree") module was loaded * unsigned module was loaded ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Model information sys_vendor: Gigabyte Technology Co., Ltd. product_name: To be filled by O.E.M. product_version: To be filled by O.E.M. chassis_vendor: Gigabyte Technology Co., Ltd. chassis_version: To Be Filled By O.E.M. bios_vendor: American Megatrends Inc. bios_version: F8d board_vendor: Gigabyte Technology Co., Ltd. board_name: F2A88XM-DS2 board_version: x.x ** Loaded modules: rtw88_8822b rtw88_core mac80211 libarc4 cfg80211 vboxnetadp(OE) vboxnetflt(OE) xt_REDIRECT xt_tcpudp vboxdrv(OE) nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink nvme_fabrics snd_seq_dummy snd_hrtimer snd_seq snd_seq_device qrtr rfkill cpufreq_ondemand cpufreq_conservative cpufreq_powersave cpufreq_userspace tun dm_raid binfmt_misc nvidia_drm(POE) drm_kms_helper nvidia_modeset(POE) nls_ascii nls_cp437 vfat fat nvidia(POE) edac_mce_amd snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio kvm_amd snd_hda_codec_hdmi ccp rng_core snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi kvm snd_hda_codec snd_hda_core snd_hwdep sp5100_tco irqbypass snd_pcm k10temp watchdog snd_timer snd soundcore joydev acpi_cpufreq evdev sg parport_pc ppdev lp parport drm fuse loop efi_pstore configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 dm_crypt dm_mod efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 raid0 multipath linear md_mod hid_generic usbhid hid uas usb_storage sd_mod nvme crc32_pclmul crc32c_intel nvme_core ahci r8169 ghash_clmulni_intel libahci sha512_ssse3 t10_pi xhci_pci sha512_generic aesni_intel libata crc64_rocksoft_generic ohci_pci ehci_pci ohci_hcd crc64_rocksoft crc_t10dif ehci_hcd xhci_hcd realtek mdio_devres scsi_mod crypto_simd cryptd crct10dif_generic i2c_piix4 libphy usbcore scsi_common crct10dif_pclmul crc64 usb_common crct10dif_common video wmi button ** PCI devices: 00:00.0 Host bridge [0600]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex [1022:1410] Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex [1022:1410] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:04.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port [1022:1414] (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Trinity A-series APU [1022:1234] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:05.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port [1022:1415] (prog-if 00 [Normal decode]) Subsystem: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Port [1022:1234] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7814] (rev 09) (prog-if 30 [XHCI]) Subsystem: Gigabyte Technology Co., Ltd FCH USB XHCI Controller [1458:5004] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:10.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7814] (rev 09) (prog-if 30 [XHCI])
Bug#1036988: crashes with TypeError: _ScrolledWindowBase.SetScrollbars(): argument 3 has unexpected type 'float'
Done. New release is up on GitHub. https://github.com/metlov/cycle With the best regards, Konstantin. Quoting Andreas Tille : Am Wed, May 31, 2023 at 05:35:46PM +0300 schrieb Konstantin L. Metlov: Thank you for reporting this bug ! It is already fixed by the commit https://github.com/metlov/cycle/commit/e86d72ec1a2a05c46ccde2f607f142cef7dbabb2 I should, probably, make a new bugfix release. A bugfix release would be welcome. Kind regards Andreas. Or, alternatively, the package can be patched with the last few cherry picked git commits. All of the latest commits are bugfixes, only one of them (merging LMB and RMB handling) changes the functionality a little bit, making the program more convenient to use on touch screen devices. With the best regards, Konstantin. Quoting cacat...@tuxfamily.org: > Package: cycle > Version: 0.3.2-2 > > Hello, > > steps to reproduce: > - run the program > - fill infos (name and password) > - validate > > The program crashes with this output on a terminal: > > ~ > $ cycle > /usr/bin/cycle:35: DeprecationWarning: Use setlocale(), getencoding() > and getlocale() instead > dl = locale.getdefaultlocale() > > (cycle:108832): dbind-WARNING **: 08:53:27.113: AT-SPI: Error retrieving > accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: > The name org.a11y.Bus was not provided by any .service files > Traceback (most recent call last): > File "/usr/bin/cycle", line 212, in OnInit > self.frame_init() > File "/usr/bin/cycle", line 216, in frame_init > frame = MyFrame(None, -1, "") > ^ > File "/usr/bin/cycle", line 81, in __init__ > self.cal = Cal_Year(self) >^^ > File "/usr/share/cycle/cal_year.py", line 168, in __init__ > self.Init_Year() > File "/usr/share/cycle/cal_year.py", line 209, in Init_Year > self.SetScrollbars(20, 20, w/20, h/20) > TypeError: _ScrolledWindowBase.SetScrollbars(): argument 3 has > unexpected type 'float' > OnInit returned false, exiting... > ~ > > Have a good day, > > > -- System Information: > Debian Release: 12.0 > APT prefers testing > APT policy: (900, 'testing'), (800, 'unstable'), (500, > 'testing-security'), (500, 'testing-debug') > Architecture: amd64 (x86_64) > > Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE > not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Versions of packages cycle depends on: > ii python3 3.11.2-1+b1 > ii python3-wxgtk4.0 4.2.0+dfsg-3 > > cycle recommends no packages. > > cycle suggests no packages. > > -- no debconf information ___ Debian-med-packaging mailing list debian-med-packag...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging -- http://fam-tille.de
Bug#1036988: crashes with TypeError: _ScrolledWindowBase.SetScrollbars(): argument 3 has unexpected type 'float'
Thank you for reporting this bug ! It is already fixed by the commit https://github.com/metlov/cycle/commit/e86d72ec1a2a05c46ccde2f607f142cef7dbabb2 I should, probably, make a new bugfix release. Or, alternatively, the package can be patched with the last few cherry picked git commits. All of the latest commits are bugfixes, only one of them (merging LMB and RMB handling) changes the functionality a little bit, making the program more convenient to use on touch screen devices. With the best regards, Konstantin. Quoting cacat...@tuxfamily.org: Package: cycle Version: 0.3.2-2 Hello, steps to reproduce: - run the program - fill infos (name and password) - validate The program crashes with this output on a terminal: ~ $ cycle /usr/bin/cycle:35: DeprecationWarning: Use setlocale(), getencoding() and getlocale() instead dl = locale.getdefaultlocale() (cycle:108832): dbind-WARNING **: 08:53:27.113: AT-SPI: Error retrieving accessibility bus address: org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not provided by any .service files Traceback (most recent call last): File "/usr/bin/cycle", line 212, in OnInit self.frame_init() File "/usr/bin/cycle", line 216, in frame_init frame = MyFrame(None, -1, "") ^ File "/usr/bin/cycle", line 81, in __init__ self.cal = Cal_Year(self) ^^ File "/usr/share/cycle/cal_year.py", line 168, in __init__ self.Init_Year() File "/usr/share/cycle/cal_year.py", line 209, in Init_Year self.SetScrollbars(20, 20, w/20, h/20) TypeError: _ScrolledWindowBase.SetScrollbars(): argument 3 has unexpected type 'float' OnInit returned false, exiting... ~ Have a good day, -- System Information: Debian Release: 12.0 APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (500, 'testing-security'), (500, 'testing-debug') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cycle depends on: ii python3 3.11.2-1+b1 ii python3-wxgtk4.0 4.2.0+dfsg-3 cycle recommends no packages. cycle suggests no packages. -- no debconf information
Bug#1035577: New upstream Dovecot stable version 2.3.20
Package: dovecot-core Version: 1:2.3.19.1+dfsg1-2.1 Severity: wishlist The current upstream version of dovecot is 2.3.20, which fixes several problems in 2.3.19 while adding almost no features. It's been remarkably problem-free on the Dovecot mailing list, compared to 2.3.19 that had numerous problem reports. If possible, it would be great to see 2.3.20 in Debian rather than 2.3.19. -- Robert L Mathews
Bug#1029736: Odoo-14 fails to start
thanks Seb;
Bug#773304: Apple reports 2022
Enviado do meu iPhone
Bug#683911: P.O 22/09/2021
On Tue, 21 Sep 2021 20:58:20 -0700 PT FINDORA INTERNUSA wrote: > Hello, > > Good morning, > > We have gone through your samples from a partner and Here is our Order > List. Please do bear in mind that we are very much in need of this > order, quote your competitive prices. > > Kindly send the Order confirmation. > > Your early reply will be much appreciated. > > Best Regards, > > Maryanah Erwin. > > PT FINDORA INTERNUSA > > Jln Pahlawan 66 Kec. Arjawinangun > > 45162 CIREBON West-Java INDONESIA > > tel : +62 231 357334 > > fax: +62 231 357260 > > email: market...@findora.com Enviado do meu iPhone
Bug#1025778: libnewuoa breaks libpdb-redo autopkgtest: pdb-redo-example (Failed)
ailure" to re-run the failed cases verbosely. autopkgtest [15:19:23]: test run-unit-test -- Maarten L. Hekkelman http://www.hekkelman.com/
Bug#1024802: new monitor that works
I bought a new monitor, confirming that it works. The problem seems to be with older devices.
Bug#1024802: here is a hw probe of my system
https://linux-hardware.org/?probe=51cf6d10e7 To reiterate this system is mostly working but headless. The only monitor I can get to work is a smart TV, dumb DP displays show no output neither does dumb tv. The screen goes blank shortly into booting Thanks, Tim
Bug#1024893: libcifpp: Requesting transition slot
Source: libcifpp Severity: normal Dear Maintainer, libcifpp and libpdb-redo are both in experimental. I've prepared the packages depending on them and am now requesting a time slot to take the following transition steps. regards, -maarten hekkelman
Bug#1024802: updated amd firmware breaks (some) display output
8] amdgpu :2d:00.0: amdgpu: ring vcn_dec_0 uses VM inv eng 0 on hub 1 [ 78.997710] amdgpu :2d:00.0: [drm] Cannot find any crtc or sizes [ 78.997713] amdgpu :2d:00.0: [drm] Cannot find any crtc or sizes 022-11-25T15:10:19.020538-05:00 debian /usr/libexec/gdm-x-session[11179]: xf86EnableIO: failed to enable I/O ports -03ff (Operation not permitted) 2022-11-25T15:10:19.020551-05:00 debian /usr/libexec/gdm-x-session[11179]: (WW) Falling back to old probe method for modesetting 2022-11-25T15:10:19.020565-05:00 debian /usr/libexec/gdm-x-session[11179]: (WW) Falling back to old probe method for fbdev 2022-11-25T15:10:19.020578-05:00 debian /usr/libexec/gdm-x-session[11179]: (II) Loading sub module "fbdevhw" 2022-11-25T15:10:19.020594-05:00 debian /usr/libexec/gdm-x-session[11179]: (II) LoadModule: "fbdevhw" 2022-11-25T15:10:19.020618-05:00 debian /usr/libexec/gdm-x-session[11179]: (II) Loading /usr/lib/xorg/modules/libfbdevhw.so 2022-11-25T15:10:19.020633-05:00 debian /usr/libexec/gdm-x-session[11179]: (II) Module fbdevhw: vendor="X.Org Foundation" 2022-11-25T15:10:19.020649-05:00 debian /usr/libexec/gdm-x-session[11179]: #011compiled for 1.21.1.4, module version = 0.0.2 2022-11-25T15:10:19.020663-05:00 debian /usr/libexec/gdm-x-session[11179]: #011ABI class: X.Org Video Driver, version 25.2 2022-11-25T15:10:19.020677-05:00 debian /usr/libexec/gdm-x-session[11179]: (EE) open /dev/fb0: No such file or directory 2022-11-25T15:10:19.020692-05:00 debian /usr/libexec/gdm-x-session[11179]: (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support 2022-11-25T15:10:19.020710-05:00 debian /usr/libexec/gdm-x-session[11179]: (II) AMDGPU(0): Creating default Display subsection in Screen section 2022-11-25T15:10:19.020724-05:00 debian /usr/libexec/gdm-x-session[11179]: #011"Default Screen Section" for depth/fbbpp 24/32 2022-11-25T15:10:19.020738-05:00 debian /usr/libexec/gdm-x-session[11179]: (==) AMDGPU(0): Depth 24, (--) framebuffer bpp 32 2022-11-25T15:10:19.020752-05:00 debian /usr/libexec/gdm-x-session[11179]: (II) AMDGPU(0): Pixel depth = 24 bits stored in 4 bytes (32 bpp pixmaps) 2022-11-25T15:10:19.020766-05:00 debian /usr/libexec/gdm-x-session[11179]: (==) AMDGPU(0): Default visual is TrueColor 2022-11-25T15:10:19.020779-05:00 debian /usr/libexec/gdm-x-session[11179]: (==) AMDGPU(0): RGB weight 888 2022-11-25T15:10:19.020793-05:00 debian /usr/libexec/gdm-x-session[11179]: (II) AMDGPU(0): Using 8 bits per RGB (8 bit DAC) 2022-11-25T15:10:19.020807-05:00 debian /usr/libexec/gdm-x-session[11179]: (--) AMDGPU(0): Chipset: "AMD Radeon RX 6500 XT" (ChipID = 0x743f) On Fri, Nov 25, 2022 at 2:58 PM Salvatore Bonaccorso wrote: > Control: tags -1 + moreinfo > > Hi Timothy, > > On Fri, Nov 25, 2022 at 08:03:51AM -0500, Timothy L. Mieszkowski wrote: > > Package: firmware-amd-graphics > > Version: 20221109-2 > > > > After upgrading to bookworm the display output for some monitors shows no > > output. There are no errors and the system is working headless. > > Tried on: Display Port monitor -- doesn't work no output > >non-smart tv -- doesn't work no output > > hdmi smart tv -- works > > > > motherboard: mag tomahawk b550 wifi motherboard > > gpu : amd rx6500 xt 4gb > > cpu: ryzen 7 5800x > > > > kernel: > > Linux debian 6.0.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.8-1 > > (2022-11-11) x86_64 GNU/Linux > > > > lspci: > > 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > > Root Complex > > 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU > > 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > > PCIe Dummy Host Bridge > > 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > GPP > > Bridge > > 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > GPP > > Bridge > > 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > > PCIe Dummy Host Bridge > > 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > > PCIe Dummy Host Bridge > > 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > GPP > > Bridge > > 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > > PCIe Dummy Host Bridge > > 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > > PCIe Dummy Host Bridge > > 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > > PCIe Dummy Host Bridge > > 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse > > Internal PCIe GPP Bridge 0 to bus[E:B] > > 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/M
Bug#1024802: updated amd firmware breaks (some) display output
Package: firmware-amd-graphics Version: 20221109-2 After upgrading to bookworm the display output for some monitors shows no output. There are no errors and the system is working headless. Tried on: Display Port monitor -- doesn't work no output non-smart tv -- doesn't work no output hdmi smart tv -- works motherboard: mag tomahawk b550 wifi motherboard gpu : amd rx6500 xt 4gb cpu: ryzen 7 5800x kernel: Linux debian 6.0.0-4-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.0.8-1 (2022-11-11) x86_64 GNU/Linux lspci: 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root Complex 00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Starship/Matisse IOMMU 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse GPP Bridge 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:05.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Host Bridge 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 61) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 5 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 6 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Matisse/Vermeer Data Fabric: Device 18h; Function 7 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO 02:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset USB 3.1 XHCI Controller 02:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset SATA Controller 02:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] 500 Series Chipset Switch Upstream Port 03:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea 03:09.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43ea 29:00.0 Network controller: MEDIATEK Corp. MT7921K (RZ608) Wi-Fi 6E 80MHz 2a:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05) 2b:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c1) 2c:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch 2d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] (rev c1) 2d:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller 2e:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse PCIe Dummy Function 2f:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP 2f:00.1 Encryption controller: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Cryptographic Coprocessor PSPCPP 2f:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller 2f:00.4 Audio device: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller
Bug#1024622: ITP: libmcfp -- A header-only C++ argv and configuration parsing library
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: libmcfp Version : 1.2.2 Upstream Author : Maarten L. Hekkelman * URL : http://github.com/mhekkel/libmcfp * License : BSD-2-Clause Programming Lang: C++ Description : A header-only C++ argv and configuration parsing library There are already a few configuration parser around, but most of them introduce runtime dependencies. This header-only library avoids that and add a simple to use and complete C++ API for accessing configuration passed through command line arguments or configuration files. The argv parsing is following the POSIX standard. All of the programs I've submitted to Debian before have switched from using boost::program_options to libcfp. Adding this library to Debian would ease packaging updates to these tools a lot. (Alternative is to include a copy of this lib to each and every tools separately). This library is intended to be maintained by the med-team. This ITP replaces the one from bug nr #1024144 which had a name conflict on other platforms.
Bug#683911: Apple reports crime 2022
Enviado do meu iPhone
Bug#1024144: ITP: libcfp -- A header-only C++ argv and configuration parsing library
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" X-Debbugs-Cc: debian-de...@lists.debian.org, maar...@hekkelman.com * Package name: libcfp Version : 1.2.0 Upstream Author : Maarten L. Hekkelman * URL : https://github.com/mhekkel/libcfp.git * License : BSD-2-Clause Programming Lang: C++ Description : A header-only C++ argv and configuration parsing library There are already a few configuration parser around, but most of them introduce runtime dependencies. This header-only library avoids that and add a simple to use and complete C++ API for accessing configuration passed through command line arguments or configuration files. The argv parsing is following the POSIX standard. All of the programs I've submitted to Debian before have switched from using boost::program_options to libcfp. Adding this library to Debian would ease packaging updates to these tools a lot. (Alternative is to include a copy of this lib to each and every tools separately).
Bug#1019495: Cross-origin requests for torrent files
Package: cdimage.debian.org Severity: wishlist Please add Access-Control-Allow-Origin: * to the HTTP headers for .torrent files. We're working on an in-browser webtorrent-powered distro downloader at https://distrorrent.github.io/ and being able to fetch up-to-date torrents directly would be nice to have. Thanks.
Bug#993014: [Pkg-samba-maint] Processed: Re: cifs-utils non-parallel FTBFS
> I think both are wrong but both do the job. Yes, I think also, but that’s not something I can do. This "fix" works fine so far, but yeah, upstream should fix it. > Now, the question is: do we need to fix this for bullseye? > It smells like there's no need to, no? No, not that I think off, current bullseye version builds as far I know, but I hardly do cifs-utils packages. its only that I needed it now on 1 server. The shown fix, commit aeaa786aceb0ea781ded2c151fb68f6b34880ad4 is the patch I added. and cifs-utils 7.0 also fails to build without that patch with parallel=1 And yes, we can leave Bullseye versions alone, but would be nice to add this one to unstable. At least the patch fixed this bug report Greetz, Louis > -Oorspronkelijk bericht- > Van: Pkg-samba-maint lists.debian.net> Namens Debian Bug Tracking System > Verzonden: donderdag 25 augustus 2022 10:15 > Aan: Michael Tokarev > CC: pkg-samba-ma...@lists.alioth.debian.org > Onderwerp: [Pkg-samba-maint] Processed: Re: cifs-utils non-parallel FTBFS > > Processing control commands: > > > tag -1 + pending > Bug #993014 [src:cifs-utils] cifs-utils non-parallel FTBFS Added tag(s) > pending. > > -- > 993014: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993014 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > ___ > Pkg-samba-maint mailing list > pkg-samba-ma...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-samba-maint
Bug#993014: cifs-utils non-parallel FTBFS
I can confirm the patch works. I've tested on a Debian Bullseye build with cifs-utils 7.0 from https://ftp.samba.org/pub/linux-cifs/cifs-utils/ I refreshed patch 001. Added the patch shown buy Helmut. And I builded against Debian Bullseye with parallel=7 and parallel=1 Only I can't upload the sources to salsa.. Sorry. @Michael Tokarev can you add this one? I can put the build and logs online if you want. Greetz, Louis
Bug#1016887: heaptrack: Grammar error in package description, misuse of contraction "it's" for possessive "its"
Package: heaptrack Version: up to current (which is 1.3.0-1) Severity: minor X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com Dear Maintainer, The Debian package description says "Heaptrack is notable for it's ability..." it should be "Heaptrack is notable for its ability..." I noticed on Bullseye but checked that it still exists up in 1.3.0-1 package on testing (Bookworm) and unstable (sid). This bug also applies to the packages libheaptrack and heaptrack-gui Small bug report but hopefully one that helps polish Debian. Thanks for what you do. Cheers, Jason Quinn -- System Information: Debian Release: 11.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-16-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages heaptrack depends on: ii libboost-iostreams1.74.01.74.0-9 ii libboost-program-options1.74.0 1.74.0-9 ii libc6 2.31-13+deb11u3 ii libgcc-s1 10.2.1-6 pn libheaptrack ii libstdc++6 10.2.1-6 heaptrack recommends no packages.
Bug#1009998: [Pkg-samba-maint] Processed: Re: Bug#1009998: gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade
Micheal, For the above link/bug reports, which points to : https://gitlab.com/samba-team/samba/-/commit/34771e1931587807d0395c7ac7f4be1 8654997f4 This fix is already included in 4.16.2. I've just verified the source of 4.16.2 Greetz, Louis > -Oorspronkelijk bericht- > Van: Pkg-samba-maint lists.debian.net> Namens Debian Bug Tracking System > Verzonden: woensdag 15 juni 2022 12:27 > Aan: Michael Tokarev > CC: pkg-samba-ma...@lists.alioth.debian.org > Onderwerp: [Pkg-samba-maint] Processed: Re: Bug#1009998: gvfs-backends: > Unable to access smb://host/sharing on any file manager after upgrade > > Processing control commands: > > > tag -1 + moreinfo > Bug #1009998 [src:samba] gvfs-backends: Unable to access > smb://host/sharing on any file manager after upgrade Added tag(s) > moreinfo. > > -- > 1009998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009998 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > ___ > Pkg-samba-maint mailing list > pkg-samba-ma...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-samba-maint
Bug#1012626: sicherboot requires dependency on systemd-boot{,-efi}
Package: sicherboot Version: 0.1.5 Severity: normal X-Debbugs-Cc: dus...@howett.net As of systemd-251.2-3, systemd-boot and systemd-boot-efi have been split out of the systemd package. This causes sicherboot to fail to install new kernels; confer bug #1012625 for the systemd report. Recommend a dependency on systemd-boot and systemd-boot-efi. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.1 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sicherboot depends on: ii binutils 2.38-4 ii efitools 1.9.2-2 ii systemd 251.2-4 ii uuid-runtime 2.38-4 sicherboot recommends no packages. sicherboot suggests no packages. -- no debconf information
Bug#1012625: systemd-boot: update to split -boot and -boot-efi out of systemd can harm working system
Package: systemd-boot Version: 251.2-4 Severity: normal X-Debbugs-Cc: dus...@howett.net The upgrade to systemd-251.2-4 removed systemd-boot and the EFI stub glue from /usr/lib/systemd/boot. This can result in an eventual failure to boot[1], especially when combined with a package such as `sicherboot` that manages the installation of secure boot signed kernels. On upgrade: --- sicherboot: Installing 5.18.1 to ESP objcopy: '/usr/lib/systemd/boot/efi/linuxia32.efi.stub': No such file objcopy: --change-section-vma .initrd=0x0300 never used objcopy: --change-section-vma .linux=0x0004 never used objcopy: --change-section-vma .cmdline=0x0003 never used objcopy: --change-section-vma .osrel=0x0002 never used run-parts: /etc/initramfs/post-update.d//zz-sicherboot exited with return code 1 dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 --- I realize that some of the burden here is on sicherboot to express a dependency on systemd-boot and systemd-boot-efi; however, this change to the systemd package has the potential to break non-sicherboot user flows as well. [1] or to upgrade to new supported versions of the bootloader transparently, potentially exposing users to security issues. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.1 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd-boot depends on: ii libc6 2.33-7 ii libsystemd-shared 251.2-4 ii systemd-boot-efi 251.2-4 Versions of packages systemd-boot recommends: ii efibootmgr 17-1 systemd-boot suggests no packages. -- no debconf information
Bug#1012341: med-config: 90med-config file missing a necessary trailing semi-colon
Package: med-config Version: 3.7 Severity: normal X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com Dear Maintainer, The file /etc/apt/apt.conf.d/90med-config has a syntax error. It is missing a trailing semi-colon for the DPkg scope. This can cause parsing errors, eg with the cupt package manager. You can confirm the bug by installing the cupt package and running "cupt why" on the command line. When a scope is used in an apt config file, the trailing semi-colon after the closing delimiter brace is necessary (as per "man 5 apt.conf"). The fix, I believe, is to merely change DPkg { Post-Invoke {"test -f /var/run/med-config.usermenu && if [ -x /usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus med ; fi ; rm -f /var/run/med-config.usermenu";}; } to DPkg { Post-Invoke {"test -f /var/run/med-config.usermenu && if [ -x /usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus med ; fi ; rm -f /var/run/med-config.usermenu";}; }; in the /etc/apt/apt.conf.d/90med-config file. I'm running bullseye so I have med-config version 3.7.0 but I just checked and the issue is still present in sid for 3.7.1. Hope that helps. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-14-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages med-config depends on: ii adduser3.118 ii blends-common 0.7.2 ii debconf [debconf-2.0] 1.5.77 ii menu 2.1.48 med-config recommends no packages. med-config suggests no packages. -- debconf information: * med-config/group: shared/med-config/usermenus: never
Bug#1011982: science-config: configuration file "90science-config" is missing semi-colon. Causes "unable to parse the config file" errors
Package: science-config Version: 1.14.2 Severity: normal X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com Dear Maintainer, Using a tool like cupt results in warnings like E: syntax error: line 8, character 1: expected: semicolon (';') E: unable to parse the config file '//etc/apt/apt.conf.d/90science-config' W: skipped the configuration file '//etc/apt/apt.conf.d/90science-config' The contents of that file are: /* * APT configuration file for science-config package */ DPkg { Post-Invoke {"test -f /var/run/science-config.usermenu && if [ -x /usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus science ; fi ; rm -f /var/run/science-config.usermenu";}; } And it appears that indeed it is missing the semi-colon to end the DPkg scope. The file should be /* * APT configuration file for science-config package */ DPkg { Post-Invoke {"test -f /var/run/science-config.usermenu && if [ -x /usr/sbin/blend-update-usermenus ] ; then /usr/sbin/blend-update-usermenus science ; fi ; rm -f /var/run/science-config.usermenu";}; }; Hope that helps. -- System Information: Debian Release: 11.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-14-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages science-config depends on: ii adduser3.118 ii blends-common 0.7.2 ii debconf [debconf-2.0] 1.5.77 ii menu 2.1.48 science-config recommends no packages. science-config suggests no packages. -- debconf information: * science-config/group: shared/science-config/useusermenus:
Bug#1011454: libreoffice-writer: fails to export to PDF
Package: libreoffice-writer Version: 1:7.3.4~rc1-1 Severity: important Dear Maintainer, I have a file with a PDF image that fail to export to PDF: the file is well formatted but the image gets lost. Only the "placeholder" is left. Note that printing to a PDF file do instead provide the right output. I'm attaching the offending image. At the moment I cannot provide the whole lowriter file, but should you need it I'll manage to obscure the text, while keeping the same format. I apologize for my system installation, but moving from ubuntu (that was per-installe on my PC) to deb is a very complex task. Best regards. G. L. G. -- System Information: Debian Release: bookworm/sid Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US: Shell: /bin/sh linked to /usr/bin/dash Init: sysvinit (via /sbin/init) LSM: AppArmor: enabled Versions of packages libreoffice-writer depends on: ii libabw-0.1-1 0.1.3-1build2 ii libc62.34-0ubuntu3 ii libe-book-0.1-1 0.1.3-2+b1 ii libepubgen-0.1-1 0.1.1-1ubuntu4 ii libetonyek-0.1-1 0.1.10-3 ii libgcc-s112.1.0-2 ii libicu71 71.1-3 ii libmwaw-0.3-30.3.21-1 ii libodfgen-0.1-1 0.1.8-2build1 ii libreoffice-base-core1:7.3.4~rc1-1 ii libreoffice-common 1:7.3.4~rc1-1 ii libreoffice-core 1:7.3.4~rc1-1 ii librevenge-0.0-0 0.0.4-6+b1 ii libstaroffice-0.0-0 0.0.7-1 ii libstdc++6 12.1.0-2 ii libuno-cppu3 1:7.3.4~rc1-1 ii libuno-cppuhelpergcc3-3 1:7.3.4~rc1-1 ii libuno-sal3 1:7.3.4~rc1-1 ii libuno-salhelpergcc3-3 1:7.3.4~rc1-1 ii libwpd-0.10-10 0.10.3-2 ii libwpg-0.3-3 0.3.3-1build2 ii libwps-0.4-4 0.4.12-2 ii libxml2 2.9.14+dfsg-1 ii ucf 3.0043 ii uno-libs-private 1:7.3.4~rc1-1 ii zlib1g 1:1.2.11.dfsg-4 Versions of packages libreoffice-writer recommends: ii libreoffice-math 1:7.3.4~rc1-1 Versions of packages libreoffice-writer suggests: pn default-jre | java8-runtime | jre ii fonts-crosextra-caladea20130214-2.1 ii fonts-crosextra-carlito20130920-1.1 pn libreoffice-base pn libreoffice-java-common Versions of packages libreoffice-core depends on: ii fontconfig 2.13.1-4.4 ii fonts-opensymbol2:102.12+LibO7.3.4~rc1-1 ii libabsl20210324 0~20210324.2-3 ii libboost-locale1.74.0 1.74.0-14+b1 ii libc6 2.34-0ubuntu3 ii libcairo2 1.16.0-5ubuntu1 ii libclucene-contribs1v5 2.3.3.4+dfsg-1+b1 ii libclucene-core1v5 2.3.3.4+dfsg-1+b1 ii libcups22.4.1op1-2 ii libcurl3-gnutls 7.83.1-1+b1 ii libdbus-1-3 1.14.0-1devuan1 ii libdconf1 0.40.0-3 ii libeot0 0.01-5+b1 ii libepoxy0 1.5.10-1 ii libexpat1 2.4.8-1 ii libexttextcat-2.0-0 3.4.5-1build1 ii libfontconfig1 2.13.1-4.4 ii libfreetype62.12.1+dfsg-2 ii libgcc-s1 12.1.0-2 ii libglib2.0-02.72.1-1 ii libgpgmepp6 1.16.0-1.2 ii libgraphite2-3 1.3.14-1 ii libgstreamer-plugins-base1.0-0 1.20.2-2 ii libgstreamer1.0-0 1.20.2-1 ii libharfbuzz-icu02.7.4-1+b1 ii libharfbuzz0b 2.7.4-1+b1 ii libhunspell-1.7-0 1.7.0-4 ii libhyphen0 2.8.8-7 ii libice6 2:1.0.10-1build1 ii libicu7171.1-3 ii libjpeg62-turbo 1:2.1.2-1 ii liblcms2-2 2.12~rc1-2 ii libldap-2.5-0 2.5.12+dfsg-1 ii libmythes-1.2-0 2:1.2.4-4 ii libnspr42:4.33-1 ii libnss3 2:3.77-1 ii libnumbertext-1.0-0 1.0.10-1 ii libopenjp2-72.4.0-6 ii liborcus-0.17-0 0.17.2-2+b1 ii liborcus-parser-0.17-0 0.17.2-2+b1 ii libpng16-16 1.6.37-5 ii libpoppler118 22.02.0-3 ii libraptor2-02.0.15-0ubuntu2 ii librdf0 1.0.17-1.2 ii libreoffice-common 1:7.3.4~rc1-1 ii librevenge-0.0-00.0.4-6+b1 ii libsm6 2:1.2.3-1build1 ii libstdc++6 12.1.0-2 ii libuno-cppu31:7.3.4~rc1-1 ii libuno-cppuhelpergcc3-3 1:7.3.4~rc1-1 ii libuno-sal3 1:7.3.4~rc1-1 ii libuno-salhelpergcc3-3
Bug#1010199: adapta-gtk-theme: Development has completely and officially ended
Package: adapta-gtk-theme Version: 3.95.0.11-2 Severity: minor Tags: upstream X-Debbugs-Cc: lorenzolucio+b...@live.it Dear maintainer, development has completely ended in 2018 and the official repository has been archived in 2020. Due to the rapid development of CSS this package is already flooding .xsession-errors with theme parsing errors and, because GTK's CSS is now compiled, end users have no easy way to fix the issue. Perhaps it is time to mark this package as obsolete and add suggested alternatives or remove it from the repository altogether. Best regards, Lorenzo adapta-gtk-theme recommends no packages. adapta-gtk-theme suggests no packages.
Bug#1007709: xterm: Sometimes xterm last lines are not shown, amd64->arm64
Package: xterm Version: 366-1 Severity: normal X-Debbugs-Cc: j.fdez.jambr...@gr.ssr.upm.es Dear Maintainer, Sometimes xterm last lines are not shown, pressing enter forces them to appear. This happen with xterm running on an amd4 machine but displayed in a raspberry-4 machine, both running bullseye /stable This don't happen when runinng xterm on the same amd64 machineis and displaying it on amd64 machines I noticed it when running clusterssh, but running xterm directy with ssh (ssh -X amm64_machine /usr/bin/X11/xterm) give me to the same result. Maybe the problem is in the arm64 machine. This arm64 machine is an rapsberrypi-4 one, and this report is sent from it. Thanks very much for your atention. -- System Information: Debian Release: 11.2 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: arm64 (aarch64) Kernel: Linux 5.10.0-12-arm64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_CRAP Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xterm depends on: ii libc6 2.31-13+deb11u2 ii libfontconfig1 2.13.1-4.2 ii libfreetype62.10.4+dfsg-1 ii libice6 2:1.0.10-1 ii libtinfo6 6.2+20201114-2 ii libutempter01.2.1-2 ii libx11-62:1.7.2-1 ii libxaw7 2:1.0.13-1.1 ii libxext62:1.3.3-1.1 ii libxft2 2.3.2-2 ii libxinerama12:1.1.4-2 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii libxt6 1:1.2.0-1 ii xbitmaps1.1.1-2.1 Versions of packages xterm recommends: ii x11-utils 7.7+5 Versions of packages xterm suggests: pn xfonts-cyrillic -- no debconf information
Bug#1002821: lyx-common: String/Bytes Problem in layout2layout.py
Package: lyx-common Version: 2.3.6-1 Severity: normal Tags: patch upstream X-Debbugs-Cc: ew...@ewhac.org Dear Maintainer, Discovered this while trying to use Editorium's LyXBook modules. layout2layout.py was konking out with "TypeError: cannot use a bytes pattern on a string-like object." After a bunch of debugging, I found some strings in the script that hadn't been bytes-ified, which seemed to fix the problem. Patch attached. Schwab -- System Information: Debian Release: bookworm/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.15.0-2-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lyx-common depends on: ii python3 3.9.8-1 ii tex-common 6.17 Versions of packages lyx-common recommends: ii lyx 2.3.6-1 lyx-common suggests no packages. -- no debconf information --- /usr/share/lyx/scripts/layout2layout.py 2020-12-01 02:33:35.0 -0800 +++ ./layout2layout.py 2021-12-29 01:04:59.614016427 -0800 @@ -484,8 +484,8 @@ i += 1 continue col = match.group(2) -if col == "collapsable": -lines[i] = match.group(1) + "collapsible" +if col == b"collapsable": +lines[i] = match.group(1) + b"collapsible" i += 1 continue @@ -703,7 +703,7 @@ # Insert the required number of arguments at the end of the style definition match = re_End.match(lines[i]) if match: -newarg = [''] +newarg = [b''] # First the optionals (this is the required order pre 2.1) if opts > 0: if opts == 1: @@ -1153,7 +1153,7 @@ if latextype == b"item_environment" and label.lower() == b"counter_enumi": lines[labeltype_line] = re_LabelType.sub(b'\\1\\2\\3Enumerate', lines[labeltype_line]) # Don't add the LabelCounter line later -counter = "" +counter = b"" # Replace # @@ -1227,12 +1227,12 @@ if options.input_file: source = open(options.input_file, 'rb') else: -source = sys.stdin +source = sys.stdin.buffer if options.output_file: output = open(options.output_file, 'wb') else: -output = sys.stdout +output = sys.stdout.buffer if options.format > currentFormat: error("Format %i does not exist" % options.format);
Bug#1000669: libgstreamer1.0-0: autoaudiosink uses wrong soundcard
Package: libgstreamer1.0-0 Version: 1.18.5-1 Severity: important X-Debbugs-Cc: carmen@belgacom.net Dear Maintainer, Since a few weeks, audio from several apps like firefox, chromium, parole or clementine is directed to the motherboard soundcard [Intel] instead of the pci soundcard [Live] of my desktop computer. As apps using directly ALSA as Audacity or MuseScore are still working fine, I suspect GStreamer. The PCI soundcard is always the first one because of the line "options snd slots=snd_emu10k1" in the /etc/modprobe.d/alsa-base.conf file. It is also ALSA's default soundcard because of the lines "defaults.ctl.!card Live" and "defaults.pcm.!card Live" in the /etc/asound.conf file I have *no PulseAudio* installed. If I temporarily disable onboard soundcard from bios for a test then audio go back to the PCI soundcard. Test of autoaudiosink does not work as expected. If I test GStreamer with "gst-launch-1.0 -v audiotestsrc ! audioconvert ! autoaudiosink" then command output shows a "GstPulseSink"... but I have no PulseAudio installed ?! Also You can see that the selected device is alsa_output.pci-_00_1b.0.analog-stereo which is the onboard one. See gst-auto.log below for details. Test of alsasink is ok. If I test GStreamer with "gst-launch-1.0 -v audiotestsrc ! audioconvert ! alsasink" then sound go the the PCI soundcard as expected See gst-alsa.log below for details. *** alsa-cards 0 [Live ]: EMU10K1 - SB Live! 5.1 SB Live! 5.1 (rev.7, serial:0x80641102) at 0xe880, irq 16 1 [Intel ]: HDA-Intel - HDA Intel HDA Intel at 0xfbaf8000 irq 33 2 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfbbfc000 irq 35 3 [C920 ]: USB-Audio - HD Pro Webcam C920 HD Pro Webcam C920 at usb-:00:1d.7-6, high speed *** gst-auto.log Setting pipeline to PAUSED ... Pipeline is PREROLLING ... /GstPipeline:pipeline0/GstAudioTestSrc:audiotestsrc0.GstPad:src: caps = audio/x-raw, rate=(int)44100, format=(string)F32LE, channels=(int)1, layout=(string)interleaved /GstPipeline:pipeline0/GstAudioConvert:audioconvert0.GstPad:src: caps = audio/x-raw, rate=(int)44100, format=(string)F32LE, channels=(int)1, layout=(string)interleaved /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0.GstGhostPad:sink.GstProxyPad:proxypad0: caps = audio/x-raw, rate=(int)44100, format=(string)F32LE, channels=(int)1, layout=(string)interleaved Redistribute latency... /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse.GstPad:sink: caps = audio/x-raw, rate=(int)44100, format=(string)F32LE, channels=(int)1, layout=(string)interleaved /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0.GstGhostPad:sink: caps = audio/x-raw, rate=(int)44100, format=(string)F32LE, channels=(int)1, layout=(string)interleaved /GstPipeline:pipeline0/GstAudioConvert:audioconvert0.GstPad:sink: caps = audio/x-raw, rate=(int)44100, format=(string)F32LE, channels=(int)1, layout=(string)interleaved Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstPulseSinkClock /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: volume = 1 /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: mute = false /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: current-device = alsa_output.pci-_00_1b.0.analog-stereo /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: volume = 1 /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: mute = false /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: current-device = alsa_output.pci-_00_1b.0.analog-stereo /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: volume = 1 /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: mute = false /GstPipeline:pipeline0/GstAutoAudioSink:autoaudiosink0/GstPulseSink:autoaudiosink0-actual-sink-pulse: current-device = alsa_output.pci-_00_1b.0.analog-stereo handling interrupt. Interrupt: Stopping pipeline ... Execution ended after 0:00:01.602219878 Setting pipeline to NULL ... Freeing pipeline ... *** gst-alsa.log Setting pipeline to PAUSED ... Pipeline is PREROLLING ... /GstPipeline:pipeline0/GstAudioTestSrc:audiotestsrc0.GstPad:src: caps = audio/x-raw, rate=(int)44100, format=(string)F64LE, channels=(int)2, layout=(string)interleaved, channel-mask=(bitmask)0x0003 /GstPipeline:pipeline0/GstAudioConvert:audioconvert0.GstPad:src: caps = audio/x-raw, rate=(int)44100, format=(string)F64LE, channels=(int)2, layout=(string)interleaved,
Bug#1000385: 4digits: Package "4digits" shows up in bullseye package list but it is not actually there.
Package: 4digits Version: 1.1.4-1+b1 Severity: normal X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com Dear Maintainer, As seen via the Synaptic package manager, there is a strange entry for "4digits" but it's listed as having download size "1 byte" in Section "unknown". Clicking on it generates the following information: Package 4digits has no available version, but exists in the database. This typically means that the package was mentioned in a dependency and never uploaded, has been obsoleted or is not available with the contents of sources.list Because 4digits is so close to the alphanumeric top of the package list, it is highly visible so whatever this issue is, it's a more prominent blemish than it might at first seem. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages 4digits depends on: ii libc6 2.31-13+deb11u2 pn python pn python-glade2 4digits recommends no packages.
Bug#967939: dvb-apps: Update dvb-apps:amd64 1.1.1+rev1500-1.2 => 1.1.1+rev1500-1.4 breaks gnutv
Hi, Bug confirmed on Bullseye (1.1.1+rev1500-1.4). gnutv only writes meta-data, no audio, no video, no subtitles…. So no errors but an empty stream. At least, 1.1.1+rev1500-1.2 from Buster can be installed on Bullseye without too much hassle and still works. Sincerely, -- Sylvain L. Sauvage
Bug#997977: /lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe!
Package: monopd Version: 0.10.2-4 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com, Debian Security Team Dear Maintainer, Recently upgraded from Buster to Bullseye. I'm not perusing "journalctl --boot" looking for errors and warnings and submitting bug reports as I tend to do after a Debian upgrade. One of the curious lines in my journal logs was /lib/systemd/system/monopd.service:8: Special user nobody configured, this is not safe! This does indeed appear to be a valid systemd warning. See commit at https://github.com/systemd/systemd/commit/bed0b7dfc0070e920d00c89d9a4fd4db8d974cf0 Marked as grave as per bug descriptions in the reportbug tool (introduces a security hole). Cheers, Jason -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages monopd depends on: ii libc6 2.31-13+deb11u2 ii libgcc-s1 10.2.1-6 ii libmuparser2v5 2.2.6.1+dfsg-1 ii libstdc++6 10.2.1-6 ii libsystemd0 247.3-6 ii lsb-base11.1.0 monopd recommends no packages. Versions of packages monopd suggests: ii gtkatlantic 0.6.3-1
Bug#997854: tlp: Misconfiguration in TLP causes complete loss of sound on some systems
Package: tlp Severity: important X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com Dear Debian Maintainer, There appears to be a severe sound issue affecting some users that may ultimately trace back to the tlp package. Please see the thread at https://bbs.archlinux.org/viewtopic.php?id=243004 and in particular comment #7 by Toolfox. I vaguely remember fixing a problem with buster that turned out to be related to tlp. And then recently I upgraded to bullseye and faced the same problem. I had no sound at all. Nothing. But "fixed" the issue merely by uninstalling the tlp package. Upon reboot, sound was back so tlp is definitely preventing sound for some users. This is a beguiling bug to track down because there's few clues to follow and nobody suspects a power management package to ultimately be the cause of such a severe sound bug. The bug may be related to whether users are on battery or wall power as comment #7 explains. I almost always use wall power so it affected me. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tlp depends on: pn hdparm ii iw 5.9-3 ii lsb-base11.1.0 ii pciutils1:3.7.0-5 ii rfkill 2.36.1-8 ii usbutils1:013-3 ii wireless-tools 30~pre9-13.1 Versions of packages tlp recommends: pn ethtool pn tlp-rdw Versions of packages tlp suggests: pn acpi-call-dkms ii linux-cpupower 5.10.70-1 ii smartmontools 7.2-1
Bug#997853: bluetooth.service: Failed to locate executable
Package: bluetooth Version: 5.55-3.1 Severity: important X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com Dear Maintainer, After a recent full-upgrade from buster to bullseye, bluetooth is not working. It appears the system is looking for the bluetooth daemon executable in the /usr/lib/bluetooth/ directory but no such directory exists. There is a directory called /usr/libexec/bluetooth/ that has a bluetoothd executable. I have tried reinstalling almost all the bluetooth-related packages hoping it might solve the issue by creating missing symlinks or whatever but it did not. I also have the bluez package installed and I wasn't certain which package to file this bug against. The output of "systemctl status bluetooth" gives: bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/bluetooth.service.d └─01-disable-sap-plugin.conf Active: failed (Result: exit-code) since Tue 2021-10-26 12:25:19 +08; 8min ago Docs: man:bluetoothd(8) Process: 4917 ExecStart=/usr/lib/bluetooth/bluetoothd --noplugin=sap (code=exited, status=203/EXEC) Main PID: 4917 (code=exited, status=203/EXEC) CPU: 4ms Oct 26 12:25:19 mycomputername systemd[1]: Starting Bluetooth service... Oct 26 12:25:19 mycomputername systemd[4917]: bluetooth.service: Failed to locate executable /usr/lib/bluetooth/bluetoothd: No such file or directory Oct 26 12:25:19 mycomputername systemd[4917]: bluetooth.service: Failed at step EXEC spawning /usr/lib/bluetooth/bluetoothd: No such file or directory Oct 26 12:25:19 mycomputername systemd[1]: bluetooth.service: Main process exited, code=exited, status=203/EXEC Oct 26 12:25:19 mycomputername systemd[1]: bluetooth.service: Failed with result 'exit-code'. Oct 26 12:25:19 mycomputername systemd[1]: Failed to start Bluetooth service. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bluetooth depends on: ii bluez 5.55-3.1 bluetooth recommends no packages. Versions of packages bluetooth suggests: ii bluez-cups 5.55-3.1 pn bluez-meshd ii bluez-obexd 5.55-3.1
Bug#997836: linuxptp's timemaster service and missing chrony package causing log errors
Package: linuxptp Version: 3.1-2.1 Severity: normal Tags: d-i X-Debbugs-Cc: jason.lee.quinn+deb...@gmail.com Dear Maintainer, Output of "journalctl -p err" was giving error lines such as Oct 25 20:34:14 mycomputername timemaster[862]: [4.900] failed to spawn /usr/sbin/chronyd: No such file or directory "timemaster" here, I believe, is referring to the systemd timemaster service from the linuxptp package on Debian (I'm not sure about that). I don't have the chrony package installed so this error makes sense for that reason. If it's true that this error traces to the linuxptp package, the error is unexpected because the linuxptp package does not list the chrony package as either recommended or suggested for installation and wasn't installed when I upgraded a couple of days ago to bullseye from buster. Trying to install the chrony package shows that it would require removing the systemd-timesyncd package. At this point, it's unclear what a user not familiar with the intricacies of timekeeping on linux should do and I'm reluctant to start uninstalling packages and risk falling down a rabbit hole. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linuxptp depends on: ii libc6 2.31-13+deb11u2 linuxptp recommends no packages. linuxptp suggests no packages.
Bug#989051: [Debian-med-packaging] Bug#989051: mrc: FTBFS on hppa - obj/mrc_rsrc.o created with wrong OS/ABI
Hi Étienne, Thank you very much for your reply. Luckily I found out the same route (using qemu) myself and fixed the problem All architectures are now green in tracker: https://buildd.debian.org/status/package.php?p=mrc regards, -maarten Op 12-09-2021 om 15:59 schreef Étienne Mollier: Hi Maarten, Maarten L. Hekkelman, on 2021-09-02: I found the underlying problem, apparently the ABI field of the ELF header should contain a flag indicating it is a Linux executable. In order to set this flag properly, I need to find out various things and perhaps it is easiest to try to figure out these myself. Is it possible to get access to a HPPA machine running Debian? I am a Debian maintainer, if that makes any difference. Without easy access to a PA-RISC machine, you can resort to Qemu. The Debian hppa port can be emulated using one of the emulators provided in the package qemu-system-misc. If you combine it with the package qemu-user-static (and also have Debian ports keyring at hand), then you can directly debootstrap a chroot able to run PA-RISC binaries: $ uname -m x86_64 $ sudo debootstrap \ --arch=hppa \ --keyring=/usr/share/keyrings/debian-ports-archive-keyring.gpg \ --include=debian-ports-archive-keyring \ sid sid-hppa-chroot http://ftp.ports.debian.org/debian-ports I: Target architecture can be executed [...] I: Base system installed successfully. $ sudo chroot sid-hppa-chroot uname -m parisc Otherwise, could you provide me the output of `cpp -dM /dev/null` and perhaps also how to detect PA-RISC/Debian in a cmake file. That last question is perhaps a bit too much to ask for, but any hint is appreciated. Feel free to checkout cpp_hppa.h in attachment; I obtained it with the aforementioned method. In hope this helps, Have a nice day, :) -- Maarten L. Hekkelman http://www.hekkelman.com/
Bug#994010: libvirt-daemon: cannot create lvm volume in logical pool if there is existing signature on that device
Package: libvirt-daemon Version: 7.0.0-3 Severity: important Dear Maintainer, I cannot create a LVM volume if there is an existing signature on that device. This happen while trying to clone a VM or to create a new VM. This bug has been comfirmed (https://bugzilla.redhat.com/show_bug.cgi?id=1940413) and patched on upstream version 7.6 (https://gitlab.com/libvirt/libvirt/-/commit/d91a3e96c04ae093f4422b52e259750c86ba79fc). I was unsure whether I should fill a bug report in order to backport a fix to stable. A workaround is to run the lvcreate command manually. But it is a nightmare when cloning a VM, as you need to create the new volume to wipe it, and remove it to clone the orignal disk. -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/16 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libvirt-daemon depends on: ii libblkid1 2.36.1-8 ii libc6 2.31-13 ii libdevmapper1.02.1 2:1.02.175-2.1 ii libgcc-s1 10.2.1-6 ii libglib2.0-02.66.8-1 ii libnetcf1 1:0.2.8-1.1 ii libparted2 3.4-1 ii libpcap0.8 1.10.0-2 ii libpciaccess0 0.16-1 ii libselinux1 3.1-3 ii libudev1247.3-6 ii libvirt-daemon-driver-qemu 7.0.0-3 ii libvirt07.0.0-3 ii libxml2 2.9.10+dfsg-6.7 Versions of packages libvirt-daemon recommends: ii libvirt-daemon-driver-lxc 7.0.0-3 ii libvirt-daemon-driver-vbox 7.0.0-3 ii libvirt-daemon-driver-xen 7.0.0-3 ii libxml2-utils 2.9.10+dfsg-6.7 ii netcat-openbsd 1.217-3 ii qemu-system-x86 [qemu-kvm] 1:5.2+dfsg-11 Versions of packages libvirt-daemon suggests: pn libvirt-daemon-driver-storage-gluster pn libvirt-daemon-driver-storage-iscsi-direct pn libvirt-daemon-driver-storage-rbd pn libvirt-daemon-driver-storage-zfs ii libvirt-daemon-system 7.0.0-3 pn numad -- no debconf information
Bug#993838: sane-utils: fails to detect scanner w/o root privileges; the user is in scanner group
В Tue, 07 Sep 2021 18:18:52 +0200 Jörg Frings-Fürst пишет: > Hello, > > at first please answer always into the bug,too. > > > First please send the output of > > systemctl status udev $ systemctl status udev ● systemd-udevd.service - Rule-based Manager for Device Events and Files Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Wed 2021-09-08 19:19:28 +07; 2s left TriggeredBy: ● systemd-udevd-kernel.socket ● systemd-udevd-control.socket Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 277 (systemd-udevd) Status: "Processing with 24 children at max" Tasks: 1 Memory: 36.6M CPU: 1.261s CGroup: /system.slice/systemd-udevd.service └─277 /lib/systemd/systemd-udevd Warning: some journal files were not opened due to insufficient permissions. # systemctl status udev ● systemd-udevd.service - Rule-based Manager for Device Events and Files Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Wed 2021-09-08 19:19:28 +07; 38s ago TriggeredBy: ● systemd-udevd-kernel.socket ● systemd-udevd-control.socket Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 277 (systemd-udevd) Status: "Processing with 24 children at max" Tasks: 1 Memory: 36.6M CPU: 1.261s CGroup: /system.slice/systemd-udevd.service └─277 /lib/systemd/systemd-udevd ... > Then check that > > ENV{DEVNAME}!="", ENV{libsane_matched}=="yes", RUN+="/bin/setfacl -m > g:scanner:rw $env{DEVNAME}" > > is in one line without linebreak before the end. OK > > Next please test: > > Add the file as root: > > /etc/udev/rules.d/scanner.rules > > > Insert this line > > SUBSYSTEMS=="usb", ATTRS{idVendor}=="07b3", ATTRS{idProduct}=="1300", > GROUP="scanner" OK > Then reboot und test it again. Scanner detected! $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. could not open USB device 0x8087/0x0024 at 002:002: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions) could not open USB device 0x046d/0xc33a at 001:004: Access denied (insufficient permissions) could not open USB device 0x062a/0x4101 at 001:003: Access denied (insufficient permissions) could not open USB device 0x8087/0x0024 at 001:002: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0003 at 004:001: Access denied (insufficient permissions) found USB scanner (vendor=0x07b3 [PLUSTEK INC], product=0x1300 [USB2.0 SCANNER], chip=GL845) at libusb:003:002 could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions) # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x07b3 [PLUSTEK INC], product=0x1300 [USB2.0 SCANNER], chip=GL845) at libusb:003:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. > If fails then give me the output of > > systemctl status udev > > again. It works! $ systemctl status udev ● systemd-udevd.service - Rule-based Manager for Device Events and Files Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static) Active: active (running) since Wed 2021-09-08 19:28:35 +07; 22s ago TriggeredBy: ● systemd-udevd-control.socket ● systemd-udevd-kernel.socket Docs: man:systemd-udevd.service(8) man:udev(7) Main PID: 280 (systemd-udevd) Status: "Processing with 24 children at max" Tasks: 1 Memory: 36.9M CPU: 1.536s CGroup: /system.slice/systemd-udevd.service └─280 /lib/systemd/systemd-udevd Warning: some journal files were not opened due to insufficient permissions. #
Bug#993839: thunderbird: vary bad look in high dpi screen; tiny fonts and icons
Package: thunderbird Version: 1:78.12.0-1 Severity: normal X-Debbugs-Cc: 507...@mail.ru Dear Maintainer, my screen dpi is 160, and the thunderbird in debian 11 looks terrible ... tears of eyes due to tiny fonts and icons ... Note that it's allright with thunderbird fonts in suse thumbleweed linux with high dpi screen ... How to correct this? WBR, Andrei L -- System Information: Debian Release: 11.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages thunderbird depends on: ii debianutils 4.11.2 ii fontconfig 2.13.1-4.2 ii libatk1.0-0 2.36.0-2 ii libbotan-2-172.17.3+dfsg-2 ii libbz2-1.0 1.0.8-4 ii libc62.31-13 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-2 ii libdbus-glib-1-2 0.110-6 ii libevent-2.1-7 2.1.12-stable-1 ii libffi7 3.3-6 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.4+dfsg-1 ii libgcc-s110.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.8-1 ii libgtk-3-0 3.24.24-4 ii libicu67 67.1-7 ii libjson-c5 0.15-2 ii libnspr4 2:4.29-1 ii libpango-1.0-0 1.46.2-3 ii libstdc++6 10.2.1-6 ii libvpx6 1.9.0-1 ii libx11-6 2:1.7.2-1 ii libx11-xcb1 2:1.7.2-1 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 ii libxext6 2:1.3.3-1.1 ii libxrender1 1:0.9.10-1 ii psmisc 23.4-2 ii x11-utils7.7+5 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages thunderbird recommends: ii hunspell-en-us [hunspell-dictionary] 1:2019.10.06-1 ii hunspell-ru [hunspell-dictionary] 1:7.1.0~rc3-3 Versions of packages thunderbird suggests: ii apparmor 2.13.6-10 ii fonts-lyx 2.3.6-1 ii libgssapi-krb5-2 1.18.3-6 ii libgtk2.0-0 2.24.33-2 -- no debconf information
Bug#993838: sane-utils: fails to detect scanner w/o root privileges; the user is in scanner group
Package: sane-utils Version: 1.0.31-4.1 Severity: normal X-Debbugs-Cc: 507...@mail.ru Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I add myself to the scanner group and plug the scanner to the usb port. (scanner:x:119:saned,andrei ) Then, I try $ sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. could not open USB device 0x8087/0x0024 at 003:002: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0002 at 003:001: Access denied (insufficient permissions) could not open USB device 0x046d/0xc33a at 001:004: Access denied (insufficient permissions) could not open USB device 0x062a/0x4101 at 001:003: Access denied (insufficient permissions) could not open USB device 0x8087/0x0024 at 001:002: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0002 at 001:001: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0003 at 004:001: Access denied (insufficient permissions) could not open USB device 0x07b3/0x1300 at 002:002: Access denied (insufficient permissions) could not open USB device 0x1d6b/0x0002 at 002:001: Access denied (insufficient permissions) # No USB scanners found. If you expected something different, make sure that # you have loaded a kernel driver for your USB host controller and have setup # the USB system correctly. See man sane-usb for details. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. # You may want to run this program as root to find all devices. Once you # found the scanner devices, be sure to adjust access permissions as # necessary. So it fails. Then I log in with root privileges and try # sane-find-scanner # sane-find-scanner will now attempt to detect your scanner. If the # result is different from what you expected, first make sure your # scanner is powered up and properly connected to your computer. # No SCSI scanners found. If you expected something different, make sure that # you have loaded a kernel SCSI driver for your SCSI adapter. found USB scanner (vendor=0x07b3 [PLUSTEK INC], product=0x1300 [USB2.0 SCANNER], chip=GL845) at libusb:002:002 # Your USB scanner was (probably) detected. It may or may not be supported by # SANE. Try scanimage -L and read the backend's manpage. # Not checking for parallel port scanners. # Most Scanners connected to the parallel port or other proprietary ports # can't be detected by this program. So it is successfully detected. What is wrong in debian 11 bullseye system settings ? WBR, Andrei L -- System Information: Debian Release: 11.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sane-utils depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.77 ii init-system-helpers1.60 ii libavahi-client3 0.8-5 ii libavahi-common3 0.8-5 ii libc6 2.31-13 ii libieee1284-3 0.2.11-14 ii libjpeg62-turbo1:2.0.6-4 ii libpng16-161.6.37-3 ii libsane1 1.0.31-4.1 ii libsystemd0247.3-6 ii libusb-1.0-0 2:1.0.24-3 ii libxml22.9.10+dfsg-6.7 ii lsb-base 11.1.0 ii update-inetd 4.51 sane-utils recommends no packages. Versions of packages sane-utils suggests: ii avahi-daemon 0.8-5 pn unpaper -- debconf information: sane-utils/saned_run: false sane-utils/saned_scanner_group: true
Bug#989051: mrc: FTBFS on hppa - obj/mrc_rsrc.o created with wrong OS/ABI
Dear Dave, Thanks for reporting, and apologies for not responding earlier. I found the underlying problem, apparently the ABI field of the ELF header should contain a flag indicating it is a Linux executable. In order to set this flag properly, I need to find out various things and perhaps it is easiest to try to figure out these myself. Is it possible to get access to a HPPA machine running Debian? I am a Debian maintainer, if that makes any difference. Otherwise, could you provide me the output of `cpp -dM /dev/null` and perhaps also how to detect PA-RISC/Debian in a cmake file. That last question is perhaps a bit too much to ask for, but any hint is appreciated. regards, -maarten Op 24-05-2021 om 20:09 schreef John David Anglin: Source: mrc Version: 1.2.3-2 Severity: normal Dear Maintainer, The build fails with the following error: make[1]: Entering directory '/<>' mrc.cpp dummy.cpp g++ -std=c++17 -o mrc-bootstrap obj/mrc.o obj/dummy.o -L/usr/lib/hppa-linux-gnu -lboost_program_options ./mrc-bootstrap -o obj/mrc_rsrc.o mrsrc.h g++ -std=c++17 -o mrc obj/mrc.o obj/mrc_rsrc.o -L/usr/lib/hppa-linux-gnu -lboost_program_options /usr/bin/ld: unknown architecture of input file `obj/mrc_rsrc.o' is incompatible with hppa1.1 output collect2: error: ld returned 1 exit status make[1]: *** [GNUmakefile:87: mrc] Error 1 As far as I can tell, this occurs because obj/mrc_rsrc.o is created with the wrong OS/ABI: dave@mx3210:~/debian/mrc/mrc-1.2.3$ file obj/mrc_rsrc.o obj/mrc_rsrc.o: ELF 32-bit MSB relocatable, PA-RISC, 1.1 version 1 (SYSV), not stripped SYSV should be GNU/Linux: dave@mx3210:~/debian/mrc/mrc-1.2.3$ file obj/mrc.o obj/mrc.o: ELF 32-bit MSB relocatable, PA-RISC, 1.1 version 1 (GNU/Linux), with debug_info, not stripped Not sure why this happens. Regards, Dave Anglin -- System Information: Debian Release: 11.0 APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: hppa (parisc64) Kernel: Linux 5.10.39+ (SMP w/4 CPU threads) Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Maarten L. Hekkelman http://www.hekkelman.com/
Bug#989705: Suspend to RAM hangs computer with nouveau driver and kernel 5.10.0-7-amd64 / 5.10.0-8-amd64
Hello, I suppose I have identified that the issue was related to the activation of the config parameter CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y in Debian Kernel 5.10.0-8-amd64 from Debian Bullseye 11.0 (it was disabled in the Debian kernel 4.19.0 from Debian Buster 10.11). This parameter was activated in Debian with linux (5.8.3-1~exp1) experimental on Mon, 24 Aug 2020 01:23:22 +0100 (see https://metadata.ftp-master.debian.org/changelogs//main/l/linux/linux_5.10.46-4_changelog) I discovered it bisecting (by hand) the diff of a working kernel config file for Debian Kernel 5.10.0-8-amd64 (generated by me from Debian kernel source code with make makeoldconfig using as template the Debian kernel config-4.19.0-11-amd64) and the default kernel config file from stock Debian Kernel 5.10.0-8-amd64 (see attachment); the "hunk" of the diff that I detected was the number 151: --- linux-source-5.10/.config 2021-08-13 17:24:22.386243765 +0200 +++ /boot/config-5.10.462021-08-01 10:27:12.0 +0200 @@ -9063,7 +9063,7 @@ # Memory initialization # CONFIG_INIT_STACK_NONE=y -CONFIG_INIT_ON_ALLOC_DEFAULT_ON=y +# CONFIG_INIT_ON_ALLOC_DEFAULT_ON is not set # CONFIG_INIT_ON_FREE_DEFAULT_ON is not set # end of Memory initialization # end of Kernel hardening options To verify this finding, I configured grub to start the kernel with the parameter init_on_alloc=0: # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="no_console_suspend nouveau.debug=warn init_on_alloc=0" [...missing...] After that, of course, I update the grub with kernel boot configuration with the command: update-grub2 The test with the stock Debian Bullseye (11.0) Kernel 5.10.0-8-amd64 was successful: I'm repeatedly able to suspend to ram and suspend to disk with parameter init_on_alloc set to 0 with the same kernel that freeze with init_on_alloc set to 1. I haven't deepened yet in kernel source code, but in theory the kernel feature activated by this parameter [1] (erase area of newly allocated memory) could have side effects with the buffer handling/eviction of memory from video memory to system memory during suspend to ram or suspend to disk. You could give it a try, even if your GPU is two year younger then mine (but they use the same nv50 kernel drm module). Let me know. [1] https://patchwork.kernel.org/project/linux-security-module/patch/20190626121943.131390-2-gli...@google.com/ --- linux-source-5.10/.config 2021-08-13 17:24:22.386243765 +0200 +++ /boot/config-5.10.46 2021-08-01 10:27:12.0 +0200 @@ -22,8 +22,8 @@ CONFIG_INIT_ENV_ARG_LIMIT=32 # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="" -# CONFIG_LOCALVERSION_AUTO is not set -CONFIG_BUILD_SALT="5.10.0-8-amd64" +CONFIG_LOCALVERSION_AUTO=y +CONFIG_BUILD_SALT="4.19.0-11-amd64" CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y @@ -114,8 +114,7 @@ CONFIG_TASK_DELAY_ACCT=y CONFIG_TASK_XACCT=y CONFIG_TASK_IO_ACCOUNTING=y -CONFIG_PSI=y -# CONFIG_PSI_DEFAULT_DISABLED is not set +# CONFIG_PSI is not set # end of CPU/Task time and stats accounting CONFIG_CPU_ISOLATION=y @@ -168,7 +167,7 @@ CONFIG_CGROUP_PIDS=y CONFIG_CGROUP_RDMA=y CONFIG_CGROUP_FREEZER=y -CONFIG_CGROUP_HUGETLB=y +# CONFIG_CGROUP_HUGETLB is not set CONFIG_CPUSETS=y CONFIG_PROC_PID_CPUSET=y CONFIG_CGROUP_DEVICE=y @@ -235,12 +234,11 @@ CONFIG_KALLSYMS_ALL=y CONFIG_KALLSYMS_ABSOLUTE_PERCPU=y CONFIG_KALLSYMS_BASE_RELATIVE=y -CONFIG_BPF_LSM=y +# CONFIG_BPF_LSM is not set CONFIG_BPF_SYSCALL=y CONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y # CONFIG_BPF_JIT_ALWAYS_ON is not set CONFIG_BPF_JIT_DEFAULT_ON=y -CONFIG_BPF_UNPRIV_DEFAULT_OFF=y # CONFIG_BPF_PRELOAD is not set CONFIG_USERFAULTFD=y CONFIG_ARCH_HAS_MEMBARRIER_SYNC_CORE=y @@ -321,7 +319,7 @@ CONFIG_X86_MPPARSE=y # CONFIG_GOLDFISH is not set CONFIG_RETPOLINE=y -CONFIG_X86_CPU_RESCTRL=y +# CONFIG_X86_CPU_RESCTRL is not set # CONFIG_X86_EXTENDED_PLATFORM is not set CONFIG_X86_INTEL_LPSS=y CONFIG_X86_AMD_PLATFORM_DEVICE=y @@ -376,11 +374,11 @@ CONFIG_HPET_EMULATE_RTC=y CONFIG_DMI=y CONFIG_GART_IOMMU=y -CONFIG_MAXSMP=y -CONFIG_NR_CPUS_RANGE_BEGIN=8192 -CONFIG_NR_CPUS_RANGE_END=8192 -CONFIG_NR_CPUS_DEFAULT=8192 -CONFIG_NR_CPUS=8192 +# CONFIG_MAXSMP is not set +CONFIG_NR_CPUS_RANGE_BEGIN=2 +CONFIG_NR_CPUS_RANGE_END=512 +CONFIG_NR_CPUS_DEFAULT=64 +CONFIG_NR_CPUS=512 CONFIG_SCHED_SMT=y CONFIG_SCHED_MC=y CONFIG_SCHED_MC_PRIO=y @@ -412,7 +410,7 @@ CONFIG_MICROCODE=y CONFIG_MICROCODE_INTEL=y CONFIG_MICROCODE_AMD=y -# CONFIG_MICROCODE_OLD_INTERFACE is not set +CONFIG_MICROCODE_OLD_INTERFACE=y CONFIG_X86_MSR=m CONFIG_X86_CPUID=m # CONFIG_X86_5LEVEL is not set @@ -423,7 +421,7 @@ CONFIG_AMD
Bug#993284: grub-efi-amd64: grub-install: using the option "--bootloader-id='custom name'" boots into the GRUB console instead of the menu
Package: grub-efi-amd64 Version: 2.04-20 Severity: normal I am in the process of making a diagnose & manteinance Debian setup onto a USB stick that can boot in whatever PC drops in my hands. Working on having a custom EFI boot entry I encountered that adding the --bootloade-id option in grub-install makes the system boot into the GRUB console instead of the usual GRUB menu. Not GRUB rescue, the regular GRUB console. I can get in there by manually bring it up with the following GRUB commands: set prefix=(hd1,gpt3)/boot #or whenever /boot/grub resides insmod normal normal I tried almost all combinations of adding --recheck, --no-nvram and --removable, but it seems that it the route isn't EFI/debian or EFI/BOOT the system won't boot on the menu. Weird enought I copied grub.cfg into EFI/[custom-name] and it seems to work, but the frame of the menu is compsided of the unknown square unicode character Currently testing on a MacBook Pro 9,2, did some test on a brand-new Lenovo L340 -- Package-specific info: *** BEGIN /proc/mounts /dev/sda4 / btrfs rw,relatime,ssd,space_cache,subvolid=256,subvol=/@rootfs 0 0 /dev/sda3 /boot ext4 rw,relatime 0 0 /dev/sda2 /boot/efi vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0 *** END /proc/mounts *** BEGIN /boot/grub/grub.cfg # # DO NOT EDIT THIS FILE # # It is automatically generated by grub-mkconfig using templates # from /etc/grub.d and settings from /etc/default/grub # ### BEGIN /etc/grub.d/00_header ### if [ -s $prefix/grubenv ]; then set have_grubenv=true load_env fi if [ "${next_entry}" ] ; then set default="${next_entry}" set next_entry= save_env next_entry set boot_once=true else set default="0" fi if [ x"${feature_menuentry_id}" = xy ]; then menuentry_id_option="--id" else menuentry_id_option="" fi export menuentry_id_option if [ "${prev_saved_entry}" ]; then set saved_entry="${prev_saved_entry}" save_env saved_entry set prev_saved_entry= save_env prev_saved_entry set boot_once=true fi function savedefault { if [ -z "${boot_once}" ]; then saved_entry="${chosen}" save_env saved_entry fi } function load_video { if [ x$feature_all_video_module = xy ]; then insmod all_video else insmod efi_gop insmod efi_uga insmod ieee1275_fb insmod vbe insmod vga insmod video_bochs insmod video_cirrus fi } if [ x$feature_default_font_path = xy ] ; then font=unicode else insmod part_gpt insmod btrfs set root='hd0,gpt4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 f54db690-2754-45a1-99f9-89dd272a4268 else search --no-floppy --fs-uuid --set=root f54db690-2754-45a1-99f9-89dd272a4268 fi font="/@rootfs/usr/share/grub/unicode.pf2" fi if loadfont $font ; then set gfxmode=auto load_video insmod gfxterm set locale_dir=$prefix/locale set lang=es_MX insmod gettext fi terminal_output gfxterm if [ "${recordfail}" = 1 ] ; then set timeout=30 else if [ x$feature_timeout_style = xy ] ; then set timeout_style=menu set timeout=5 # Fallback normal timeout code in case the timeout_style feature is # unavailable. else set timeout=5 fi fi ### END /etc/grub.d/00_header ### ### BEGIN /etc/grub.d/05_debian_theme ### insmod part_gpt insmod btrfs set root='hd0,gpt4' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4 f54db690-2754-45a1-99f9-89dd272a4268 else search --no-floppy --fs-uuid --set=root f54db690-2754-45a1-99f9-89dd272a4268 fi insmod png if background_image /@rootfs/usr/share/desktop-base/homeworld-theme/grub/grub-4x3.png; then set color_normal=white/black set color_highlight=black/white else set menu_color_normal=cyan/blue set menu_color_highlight=white/blue fi ### END /etc/grub.d/05_debian_theme ### ### BEGIN /etc/grub.d/10_linux ### function gfxmode { set gfxpayload="${1}" } set linux_gfx_mode= export linux_gfx_mode menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-f54db690-2754-45a1-99f9-89dd272a4268' { load_video insmod gzio if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi insmod part_gpt insmod ext2 set root='hd0,gpt3' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt3 --hint-efi=hd0,gpt3 --hint-baremetal=ahci0,gpt3 fb944508-a5a3-48b4-b4df-8037ae333f1d else search --no-floppy --fs-uuid --set=root fb944508-a5a3-48b4-b4df-8037ae333f1d fi echo'Loading Linux 5.10.0-8-amd64 ...' linux /vmlinuz-5.10.0-8-amd64
Bug#991907: libkpimgapicore5abi1: Kmail randomly prompts to reauthorize via OAuth2 when using Google Workspace accounts
Package: libkpimgapicore5abi1 Version: 20.08.3-1 Severity: important Tags: upstream patch X-Debbugs-Cc: ronoa...@gmail.com Dear Maintainer, I'm using Debian Bullseye as daily driver for a couple of months, and recently setup Kmail for both my personal Gmail and Workspace accounts, so I can have GPG signature and offline e-mail support in KDE. The personal account is working great, but after following some suggestions in [1] for my professional account, I am now prompted randomly to re-authorize Akonadi with the same OAuth dialog and no new permission is required. This issue seems to be fixed upstream by the KDE developers, and the fix is quite a simple one-liner patch. I have verified the patch applies against current Bullseye version, and I'm going to try the fix on my machine. I have not yet tested the new experimental packages, don't wanto to bring too many dependencies from unstable now, but I can try in a VM if that helps! [1] https://www.reddit.com/r/kde/comments/kwsmhb/how_to_add_a_google_workplace_account_to_kde/ [2] https://invent.kde.org/pim/libkgapi/-/merge_requests/17/diffs -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.13.5-amd64 (SMP w/24 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libkpimgapicore5abi1 depends on: ii kio 5.78.0-5 ii libc62.31-13 ii libkf5kiowidgets55.78.0-5 ii libkf5wallet-bin 5.78.0-2 ii libkf5wallet55.78.0-2 ii libkf5windowsystem5 5.78.0-2 ii libkpimgapi-data 20.08.3-1 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5gui5 5.15.2+dfsg-9 ii libqt5network5 5.15.2+dfsg-9 ii libqt5webengine5 5.15.2+dfsg-3 ii libqt5webenginewidgets5 5.15.2+dfsg-3 ii libqt5widgets5 5.15.2+dfsg-9 ii libstdc++6 10.2.1-6 libkpimgapicore5abi1 recommends no packages. libkpimgapicore5abi1 suggests no packages. -- no debconf information
Bug#392550: Project !!
My greetings to you. Please, kindly let me know your thoughts towards the project funding. Best regards, James L. Accredited Broker
Bug#392550: YOUR THOUGHT?
Hello, My greetings to you. Please, kindly let me know your thoughts towards about the project funding. Best regards, James L. Smith Accredited Broker
Bug#990717: xen-system-amd64: Microcode isn't loaded when booting in xen mode
Package: xen-system-amd64 Version: 4.11.4+107-gef32c7afa2-1 Severity: important Dear Maintainer, When booting in Xen mode my system doen't load microcode, I suposse this is the reason I have a line in /var/log/kern.log saying: |Jun 28 17:09:28 xuxa3 kernel: [3.013020] Performance Events: unsupported p6 CPU model 79 no PMU driver, software events only And perfomamce is degraded: When booting the system in normal mode, no xen mode, the first two lines written in /var/log/kern.log say: | Jul 5 14:05:17 xuxa3 kernel: [0.00] microcode: microcode updated early to revision 0xb3e, date = 202 1-02-06 | Jul 5 14:05:17 xuxa3 kernel: [0.00] Linux version 4.19.0-17-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-1 (2021-06-10) In xen mode the first line insn't written at all. I can't remenber if the first time I installed xen the microcode was loaded or not, but as long as I can check the microcode isn't loaded and the system performance is clearly degraded. Yours, Jose L. -- System Information: Debian Release: 10.10 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-17-amd64 (SMP w/8 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xen-system-amd64 depends on: ii xen-hypervisor-4.11-amd64 4.11.4+107-gef32c7afa2-1 ii xen-hypervisor-common 4.11.4+107-gef32c7afa2-1 ii xen-utils-4.11 4.11.4+107-gef32c7afa2-1 xen-system-amd64 recommends no packages. xen-system-amd64 suggests no packages. -- no debconf information
Bug#920900: I'm James L. Smith
Hello, My greetings to you. Please, kindly let me know your thoughts towards project funding. Best regards, James L. Smith Accredited Broker
Bug#967972: [Pkg-samba-maint] Bug#967972: cifs-utils: fails to mount filesystem when keyutils is not installed
That is already set See closed bug in cifs-utils, bugnr.: #986867 Greetz, Louis > -Oorspronkelijk bericht- > Van: Pkg-samba-maint > [mailto:pkg-samba-maint-bounces+belle=bazuin.nl@alioth-lists.d ebian.net] Namens Jonathon Reinhart > Verzonden: maandag 7 juni 2021 6:33 > Aan: 967...@bugs.debian.org > Onderwerp: [Pkg-samba-maint] Bug#967972: cifs-utils: fails to > mount filesystem when keyutils is not installed > > Some sources incorrectly indicate that keyutils is only needed with > DFS, but keyutils is also needed when using CIFS w/ Kerberos > authentication. > > When trying to mount a CIFS share using kerberos (sec=krb5), the > kernel invokes /sbin/request-key to request a key from userspace. Then > cifs.upcall (from cifs-utils) is executed to handle the SPNEGO > authentication. > > If keyutils is not installed, then /sbin/request-key is absent, and > the kernel is completely silent about this. > > [ +0.497021] CIFS VFS: Send error in SessSetup = -2 > [ +0.000992] CIFS VFS: cifs_mount failed w/return code = -2 > > Thus, I strongly agree with the proposal for cifs-utils to *Recommend* > keyutils, rather than merely *Suggesting* it. > > ___ > Pkg-samba-maint mailing list > pkg-samba-ma...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-s > amba-maint > >
Bug#988596: Acknowledgement (akonadi-server: akonadi crashes permanently; akonadiconsole does not start)
The problem also exists for a new added user (# adduser). WBR, A.
Bug#988606: logrotate script creates logfile with wrong group
Package: clamav-freshclam Version: 0.103.2 postinst creates a logrotate config that creates new log files with group "adm". That used to be fine, but newer versions of clam seem to update the group of the log file to the clam process' group whenever clam restarts. That group is usually "clamav" and almost always isn't "adm". the result is that the log file gets created with one group by logrotate, but then gets changed when clam restarts. this confuses IDS tools like AIDE. postinst should be changed so that the newly created logfile has the user and group of the user that clam runs as. smime.p7s Description: S/MIME Cryptographic Signature
Bug#988605: logrotate config creates log file with wrong group
Package: clamav-daemon Version: 0.103.2 postinst creates a logrotate config that creates new log files with group "adm". That used to be fine, but newer versions of clam seem to update the group of the log file to the clam process' group whenever clam restarts. That group is usually "clamav" and almost always isn't "adm". the result is that the log file gets created with one group by logrotate, but then gets changed when clam restarts. this confuses IDS tools like AIDE. postinst should be changed so that the newly created logfile has the user and group of the user that clam runs as. smime.p7s Description: S/MIME Cryptographic Signature
Bug#988596: Acknowledgement (akonadi-server: akonadi crashes permanently; akonadiconsole does not start)
This akonadi problem arises after full-upgrade debian 10 up to debian 11 ... I saw it on two machines. WBR, A.
Bug#988596: akonadi-server: akonadi crashes permanently; akonadiconsole does not start
This akonadi problem arises after dist-upgrade from debian 10 ... I see it on two my machines. WBR, Andrei
Bug#988438: file mode not updated when upgrading from 0.16 to 0.17
Package: aide Version: 0.17.3-2 Hello. file /etc/aide/aide.conf.d/31_aide_sudo has mode 755 in version 0.16, but mode 644 in version 0.17 that's fine in and of itself, as the contents of the file have changed. a clean install of 0.16 works fine. a clean install of 0.17 works fine too. if you upgrade from 0.16 to 0.17, the upgrade process installs the new version of 31_aide_sudo but does *not* update the mode bits. You end up with the new version of the file, but it has mode 755. This causes aide to error out. easy fix is to chmod 644 /etc/aide/aide.conf.d/31_aide_sudo post-upgrade, but ideally the installer should take care of that. it looks like the postinst script already does this for 31_aide_smokeping; I'd suggest the same for 31_aide_sudo smime.p7s Description: S/MIME Cryptographic Signature
Bug#987436: libcifpp: [INTL:pt_BR] Brazilian Portuguese debconf templates translation
Hi Adriano, Thanks very much -maarten Op 23-04-2021 om 21:41 schreef Adriano Rafael Gomes: Package: libcifpp Tags: l10n patch Severity: wishlist Hello, Please, Could you update the Brazilian Portuguese Translation? Attached you will find the file pt_BR.po. It is UTF-8 encoded and it is tested with msgfmt and podebconf-display-po. Kind regards. -- Maarten L. Hekkelman http://www.hekkelman.com/
Bug#985356: spamass-milter: all messages have score 0 UNPARSEABLE_RELAY
Package: spamass-milter Version: 0.4.0-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, freshly installed postfix + spamassasin on buster, all messages come with score 0, test message below --- X-Test-Header4: t...@lelik.org X-Test-Header3: This is a test header31. Return-Path: X-Original-To: t...@lelik.org Delivered-To: chan...@lelik.org Received: from mhost22.ispserver.com (mhost22.ispserver.com [82.202.175.117]) by mail.lelik.us (Postfix) with ESMTPS id 4F0FD70d3Pz3xgk for ; Tue, 16 Mar 2021 16:55:19 +0300 (MSK) Received: from ip-79-111-14-215.bb.netbynet.ru ([79.111.14.215] helo=[192.168.4.6]) by mhost22.ispserver.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94) (envelope-from ) id 1lMAAC-0006zf-Ei for t...@lelik.org; Tue, 16 Mar 2021 16:55:12 +0300 To: t...@lelik.org From: =?UTF-8?B?0JDQvdC00YDQtdC5INCb0LXQu9C40LrQvtCy?= Subject: s Message-ID: <33552efc-71d0-8de3-1ec5-953fcbe66...@ulybkasnt.ru> Date: Tue, 16 Mar 2021 16:55:12 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: ad...@ulybkasnt.ru X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on mail.lelik.us s --- -- System Information: Debian Release: 10.8 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'buster'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-14-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spamass-milter depends on: ii adduser 3.118 ii libc6 2.28-10 ii libgcc1 1:8.3.0-6 ii libmilter1.0.1 8.15.2-14~deb10u1 ii libstdc++6 8.3.0-6 ii spamc 3.4.2-1+deb10u2 Versions of packages spamass-milter recommends: ii postfix 3.4.14-0+deb10u1 ii spamassassin 3.4.2-1+deb10u2 spamass-milter suggests no packages. -- Configuration Files: /etc/default/spamass-milter changed: OPTIONS="-u spamass-milter -i 127.0.0.1" OPTIONS="${OPTIONS} -- -s 10485760" -- no debconf information
Bug#862139: [flash-kernel] Please, stop flashing multiple times
Le dimanche 7 février 2021, 05:03:56 CET Vagrant Cascadian a écrit : >[…] > > update-initramfs: Generating /boot/initrd.img-3.16.0-4-kirkwood > > flash-kernel: installing version 3.16.0-4-kirkwood > > Generating kernel u-boot image... done. > > Flashing kernel (2074936/2097152 bytes)... done. > > Flashing initramfs (5140458/9437184 bytes)... done. > > ... > > > Traitement des actions différées (« triggers ») pour flash-kernel > > (3.35+deb8u3) ... flash-kernel: installing version > > 3.16.0-4-kirkwood > > Generating kernel u-boot image... done. > > Flashing kernel (2074936/2097152 bytes)... done. > > Flashing initramfs (5140458/9437184 bytes)... done. > > This is almost certainly because flash-kernel has hooks in both the > kernel and initramfs: > > /etc/kernel/postinst.d/zz-flash-kernel > /etc/kernel/postrm.d/zz-flash-kernel > /etc/initramfs/post-update.d/flash-kernel > > I don't see a great way around this, as flash-kernel needs to be > updated when either gets updated, and they may often happen at the > same time. The triggers do at least prevent it from getting updated > every time a relevent package gets updated, even it if still happens > multiple times in any given run... > > > That said, someone with a better understanding of dpkg triggers might > be able to come up with something better... The problem is twofold: 1. Both changing the kernel and changing the initramfs trigger the flashing (which is okay) but the deferred trigger should be executed only once, which it’s not. (I’m not sure anymore that was the case, that was 4 years ago. I guess not as I’m talking about “flashing three times.”) 2. As (badly) shown on the excerpt the files are flashed both just when the package is installed (immediate) and when the whole update is finished (deferred). -- Sylvain L. Sauvage
Bug#980353: feed2imap: missing dependency on ruby-rubymail
Package: feed2imap Version: 1.2.6-1 Severity: important ruby-rubymail dependency was removed, but it’s still needed. Here’s the error message when ruby-rubymail is not installed (note that it’s not obvious “rmail” refers to ruby-rubymail and not ruby-mail): $ feed2imap Traceback (most recent call last): 13: from /usr/bin/feed2imap:23:in `' 12: from /usr/bin/feed2imap:23:in `load' 11: from /usr/share/rubygems- integration/all/gems/feed2imap-1.2.6/bin/feed2imap:5:in `' 10: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 9: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 8: from /usr/share/rubygems- integration/all/gems/feed2imap-1.2.6/lib/feed2imap/feed2imap.rb:23:in `' 7: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 6: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 5: from /usr/share/rubygems- integration/all/gems/feed2imap-1.2.6/lib/feed2imap/config.rb:24:in `' 4: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 3: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' 2: from /usr/share/rubygems- integration/all/gems/feed2imap-1.2.6/lib/feed2imap/maildir.rb:22:in `' 1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require' /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in `require': cannot load such file -- rmail (LoadError) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.4-zef (SMP w/16 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages feed2imap depends on: ii ruby 1:2.7+2 ii ruby-feedparser 0.9.6-1 feed2imap recommends no packages. Versions of packages feed2imap suggests: pn imap-server ii kmail [imap-client] 4:20.08.3-1 -- no debconf information -- Sylvain L. Sauvage
Bug#979314: libccp4: The endianness check in ccp4_sysdep.h is incorrect assuming powerpc is always big endian
Source: libccp4 Version: 6.5.1-4 Severity: grave Tags: patch upstream Justification: renders package unusable X-Debbugs-Cc: maar...@hekkelman.com -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 5.4.0-58-generic (SMP w/12 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect The file ccp4_sysdep.h checks for the endianness in an incorrect way, the check assumes powerpc is always big endian. By moving the catch-all test up the test is more robust. regards, -maarten --- a/ccp4/ccp4_sysdep.h +++ b/ccp4/ccp4_sysdep.h @@ -177,6 +177,26 @@ #define DFNTF_CONVEXNATIVE 5/**< Convex native floats */ #define DFNTF_LEIEEE4 /**< little-endian IEEE format */ +/* From time to time new architectures are added here, often because Linux + * packagers want to build it on all platforms supported by their distro. + * Here we try to catch machines not listed explicitely above, under + * assumption that endianness is the same for floating point numbers + * as for integers. Which is safe assumption on modern standard computers + * (not embedded systems), according to + * http://en.wikipedia.org/wiki/Endianness#Floating-point_and_endianness + */ +#if defined(__BYTE_ORDER) +# if __BYTE_ORDER == __LITTLE_ENDIAN +# define NATIVEIT DFNTI_IBO +# define NATIVEFT DFNTF_LEIEEE +# elif __BYTE_ORDER == __BIG_ENDIAN +# define NATIVEIT DFNTI_MBO +# define NATIVEFT DFNTF_BEIEEE +# endif +#endif + +#if !defined(NATIVEIT) && !defined(NATIVEFT) + #if defined (VAX) || defined (vax) /* gcc seems to use vax */ # define NATIVEFT DFNTF_VAX # define NATIVEIT DFNTI_IBO @@ -222,22 +242,6 @@ # endif #endif -/* From time to time new architectures are added here, often because Linux - * packagers want to build it on all platforms supported by their distro. - * Here we try to catch machines not listed explicitely above, under - * assumption that endianness is the same for floating point numbers - * as for integers. Which is safe assumption on modern standard computers - * (not embedded systems), according to - * http://en.wikipedia.org/wiki/Endianness#Floating-point_and_endianness - */ -#if !defined(NATIVEIT) && !defined(NATIVEFT) && defined(__BYTE_ORDER) -# if __BYTE_ORDER == __LITTLE_ENDIAN -# define NATIVEIT DFNTI_IBO -# define NATIVEFT DFNTF_LEIEEE -# elif __BYTE_ORDER == __BIG_ENDIAN -# define NATIVEIT DFNTI_MBO -# define NATIVEFT DFNTF_BEIEEE -# endif #endif #ifndef NATIVEFT
Bug#978648: spyder: Exits at startup with an import error for module zmq.backend.cython
Package: spyder Version: 3.3.6+dfsg1-5 Severity: grave Justification: renders package unusable X-Debbugs-Cc: carmen@belgacom.net Dear Maintainer, Since the last update of my Debian Testing distro, Spyder no more starts. When launching spyder from command line we can see a import error message from the python interpreter complaining that it cannot import name 'constants' from partially initialized module 'zmq.backend.cython'. And that's most likely due to a circular import (/usr/lib/python3/dist-packages/zmq/backend/cython/__init__.py) See attached traceback. Thanks. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-5-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_FIRMWARE_WORKAROUND Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), LANGUAGE=fr_BE:fr Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages spyder depends on: ii python3-spyder 3.3.6+dfsg1-5 ii python3.8 3.8.7-1 spyder recommends no packages. spyder suggests no packages. Versions of packages python3-spyder depends on: ii libjs-jquery3.5.1+dfsg+~3.5.4-3 ii libjs-mathjax 2.7.9+dfsg-1 ii pylint 2.6.0-1 ii python3 3.9.0-4 ii python3-chardet 3.0.4-7 ii python3-cloudpickle 1.6.0-1 ii python3-jedi0.17.0-1 ii python3-keyring 21.6.0-1 ii python3-nbconvert 5.6.1-2 ii python3-numpydoc1.1.0-3 ii python3-pickleshare 0.7.5-3 ii python3-psutil 5.7.3-1+b2 ii python3-pycodestyle 2.6.0-1 ii python3-pyflakes2.2.0-2 ii python3-pygments2.7.1+dfsg-1 ii python3-qtawesome 0.4.4+ds1-3 ii python3-qtconsole 4.7.6-1 ii python3-qtpy1.9.0-3 ii python3-rope0.17.0-1 ii python3-sphinx 3.3.1-1 ii python3-spyder-kernels 1.5.0~really0.5.2-1 ii python3-zmq 20.0.0-1+b1 ii spyder-common 3.3.6+dfsg1-5 Versions of packages python3-spyder suggests: pn cython3 ii python3-matplotlib 3.3.2-2+b1 ii python3-numpy 1:1.19.4-1+b1 pn python3-pandas ii python3-pil 8.0.1-1+b1 pn python3-scipy pn python3-sympy Versions of packages python3-pyqt5 depends on: ii libc6 2.31-6 ii libgcc-s1 10.2.1-1 ii libpython3.9 3.9.1-1 ii libqt5core5a [qtbase-abi-5-15-2] 5.15.2+dfsg-2 ii libqt5dbus5 5.15.2+dfsg-2 ii libqt5designer5 5.15.2-3 ii libqt5gui55.15.2+dfsg-2 ii libqt5help5 5.15.2-3 ii libqt5network55.15.2+dfsg-2 ii libqt5printsupport5 5.15.2+dfsg-2 ii libqt5test5 5.15.2+dfsg-2 ii libqt5widgets55.15.2+dfsg-2 ii libqt5xml55.15.2+dfsg-2 ii libstdc++610.2.1-1 ii python3 3.9.0-4 ii python3-pyqt5.sip 12.8.1-1+b2 Versions of packages python3-pyqt5 suggests: pn python3-pyqt5-dbg -- no debconf information Traceback (most recent call last): File "/usr/bin/spyder", line 11, in load_entry_point('spyder==3.3.6', 'gui_scripts', 'spyder3')() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 473, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2843, in load_entry_point return ep.load() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2447, in load return self.resolve() File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2453, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib/python3/dist-packages/spyder/app/start.py", line 14, in import zmq File "/usr/lib/python3/dist-packages/zmq/__init__.py", line 55, in from zmq import backend File "/usr/lib/python3/dist-packages/zmq/backend/__init__.py", line 40, in reraise(*exc_info) File "/usr/lib/python3/dist-packages/zmq/utils/sixcerpt.py", line 34, in reraise raise value File "/usr/lib/python3/dist-packages/zmq/backend/__init__.py", line 27, in _ns = select_backend(first) File "/usr/lib/python3/dist-packages/zmq/backend/select.py", line 28, in select_backend mod = __import__(name, fromlist=public_api) File "/usr/lib/python3/dist-packages/zmq/backend/cython/__init__.py", line 6, in from . import (constants, error, message, context, ImportError: cannot import name 'constants' from partially initialized module 'zmq.backend.cython' (most likely due to a circular import) (/usr/lib/python3/dist-packages/zmq/backend/cython/__init__.py)
Bug#976849: ITP: density-fitness -- Calculates per-residue electron density scores real-space R, real-space correlation coefficient, EDIAm, and OPIA
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" * Package name: density-fitness Version : 1.0.0 Upstream Author : Maarten L. Hekkelman * URL : https://github.com/PDB-REDO/density-fitness * License : BSD-2-Clause Programming Lang: C++ Description : Calculates per-residue electron density scores real-space R, real-space correlation coefficient, EDIAm, and OPIA The program density-fitness calculates electron density metrics, for main- (includes Cβ atom) and side-chain atoms of individual residues. For this calculation, the program uses the structure model in either PDB or mmCIF format and the electron density from the 2mFo-DFc and mFo-DFc maps. If these maps are not readily available, the MTZ file and model can be used to calculate maps clipper. Density-fitness support both X-ray and electron diffraction data. This program is essentially a reimplementation of _edstats_, a program available from the CCP4 suite. However, the output now contains only the RSR, SRSR and RSCC fields as in _edstats_ with the addition of EDIAm and OPIA and no longer requires pre-calculated map coefficients. The software uses libpdb-redo, libcifpp and libzeep.
Bug#976727: ITP: libpdb-redo -- Library containing shared code for the various programs in project PDB-REDO
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" * Package name: libpdb-redo Version : 1.0.0 Upstream Author : Maarten L. Hekkelman * URL : https://github.com/PDB-REDO/libpdb-redo * License : BSD-2-Clause Programming Lang: C++ Description : Library containing shared code for the various programs in project PDB-REDO For the PDB-REDO project, a lot of programs have been created over time. Many of these application share common routines and these are combined in this particular library. The PDB-REDO tools that are of general interest will follow as separate Debian packages. About PDB-REDO: PDB-REDO is a procedure to optimise crystallographic structure models, providing algorithms that make a fully automated decision making system for refinement, rebuilding and validation. It combines popular crystallographic software from CCP4, e.g. REFMAC and COOT, with with our specially developed rebuilding tools Centrifuge, Pepflip & SideAide and structure analysis tools like WHAT IF and PDB-care. PDB-REDO optimises refinement settings (e.g. geometric and B-factor restraint weights, B-factor model, TLS groups, NCS and homology restraints), refines with REFMAC, partially rebuilds the structure (rejects waters, refines side chains, checks peptide planes), refines some more, and then validates the results. With PDB-REDO you can obtain updated and optimised versions of existing entries of the PDB from our DataBank, or you can optimise your own structure model using our Server. If you want to know more or install PDB-REDO on your own computers, please check below.
Bug#976627: libcifpp: [INTL:de] initial German debconf translation
Thank Helge, I've placed the file where it is supposed to be, will be included at the next check-in. regards, -maarten Op 06-12-2020 om 05:49 schreef Helge Kreutzmann: Package: libcifpp Version: 1.0.0-3 Severity: wishlist Tags: patch l10n Please find the initial German debconf translation for libcifpp attached. Please place this file in debian/po/ as de.po for your next upload. If you update your template, please use 'msgfmt --statistics ' to check the po-files for fuzzy or untranslated strings. If there are such strings, please contact me so I can update the German translation. Greetings Helge
Bug#976272: ITP: libnewuoa-cpp -- C++ implementation of the NEWUOA algorithm
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" * Package name: libnewuoa-cpp Version : 0.1.0 Upstream Author : Roman Siromakha * URL : https://github.com/elsid/newuoa-cpp * License : MIT Programming Lang: C++ Description : C++ implementation of the NEWUOA algorithm This library contains the C++ implementation of the NEWUOA derivative free optmization algorithm originally published by Michael J. D. Powell.
Bug#975691: ITP: tortoize -- Application to calculate ramachandran z-scores.
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" * Package name: tortoize Version : 2.0.0 Upstream Author : Maarten L. Hekkelman * URL : http://github.com/PDB-REDO/tortoize * License : BSD-2-Clause Programming Lang: C++ Description : Application to calculate ramachandran z-scores. Tortoize validates protein structure models by checking the Ramachandran plot and side-chain rotamer distributions. Quality Z-scores are given at the residue level and at the model level (ramachandran-z and torsions-z). Higher scores are better. To compare models or to describe the reliability of the model Z-scores jackknife- based standard deviations are also reported (ramachandran-jackknife-sd and torsion-jackknife-sd). This application depends on libcifpp and libzeep.
Bug#975526: ITP: cif-tools -- Suite of tools to manipulate, validate and query mmCIF files
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" * Package name: cif-tools Version : 1.0.0 Upstream Author : Maarten L. Hekkelman * URL : http://github.com/PDB-REDO/cif-tools * License : BSD-2-Clause Programming Lang: C++ Description : Suite of tools to manipulate, validate and query mmCIF files This package contains a suite of tools for the manipulation of mmCIF files. The structure of macro molecules is nowadays recorded in mmCIF files. Until recently however the ancient PDB file format was used by many programs but that format has since long been deprecated. This package provides two tools, pdb2cif and cif2pdb, that can convert files from one format into the other, provided that data fits of course. Other tools are cif-validate, cif-grep, cif-diff, cif-merge and mmCQL. The latter can be used to manipulate an mmCIF file as if it were a SQL like database using SELECT, UPDATE, INSERT and DELETE commands. This package depends on libcifpp.
Bug#975446: libzeep: FTBFS against boost_1.74
Hi Anton, Previous versions of libboost-tools-dev used to install a file called boost-build.jam in /usr/share/boost-build. Version 1.74 however no longer does this. Is this a permanent change? In the previous setup one could simply use bjam to build but with version 1.74 this no longer works. So before I change my build scripts, I'd like to know if the omission of /usr/share/boost-build/boost-build.jam is an error or was intended to be dropped. regards, -maarten Op 22-11-2020 om 21:43 schreef Anton Gladky: Hi Marteen, there are really some misunderstandings with version numbers. Anyway, I have just tried to build 5.0.2-3 and it still fails to build: mkdir -p obj cd doc; /usr/bin/bjam /bin/bash /root/mod2/libzeep-5.0.2/libtool --silent --tag=CXX --mode=compile g++ -std=c++17 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/root/mod2/libzeep-5.0.2=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include -Wall -Wno-multichar -I include -O3 -DNDEBUG -MT obj/connection.lo -MD -MP -MF obj/connection.d -c -o obj/connection.lo lib-http/src/connection.cpp /bin/bash /root/mod2/libzeep-5.0.2/libtool --silent --tag=CXX --mode=compile g++ -std=c++17 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/root/mod2/libzeep-5.0.2=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include -Wall -Wno-multichar -I include -O3 -DNDEBUG -MT obj/controller.lo -MD -MP -MF obj/controller.d -c -o obj/controller.lo lib-http/src/controller.cpp /bin/bash /root/mod2/libzeep-5.0.2/libtool --silent --tag=CXX --mode=compile g++ -std=c++17 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/root/mod2/libzeep-5.0.2=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include -Wall -Wno-multichar -I include -O3 -DNDEBUG -MT obj/controller-rsrc.lo -MD -MP -MF obj/controller-rsrc.d -c -o obj/controller-rsrc.lo lib-http/src/controller-rsrc.cpp Unable to load B2: could not find 'boost-build.jam' --- Attempted search from '/root/mod2/libzeep-5.0.2/doc' up to the root at '/usr/bin/b2' Please consult the documentation at 'https://boostorg.github.io/build/'. Could you please have a look? Thanks Anton Am So., 22. Nov. 2020 um 21:22 Uhr schrieb Maarten L. Hekkelman : Hi, The bug report is for libzeep version 5, but the logs show that an attempt was made to compile version 3. I'm quite sure that building libzeep version 5 with boost 1.74 will succeed, since I've been using it myself for several weeks now. regards, -maarten Op 22-11-2020 om 13:28 schreef Anton Gladky: Package: libzeep Version: 5.0.2-3 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most relevant part is probably this: dpkg-source: info: using options from libzeep-3.0.5/debian/source/options: --extend-diff-ignore=(^|/)(.vscode/.*|msvc|\.gitignore|\.travis\.yml|tests|zeep-test.*|webapp-test.cpp|doc/bin)$ fakeroot debian/rules clean dh clean dh_auto_clean make -j4 clean make[1]: Entering directory '/<>' rm -rf obj/* libzeep.a libzeep.so* zeep-test libzeep-3.0.5 libzeep-3.0.5.tgz cd doc; bjam clean Unable to load B2: could not find 'boost-build.jam' - --- Attempted search from '/<>/doc' up to the root at '/usr/bin/b2' Please consult the documentation at 'https://boostorg.github.io/build/'. make[1]: *** [makefile:122: clean] Error 1 make[1]: Leaving directory '/<>' dh_auto_clean: error: make -j4 clean returned exit code 2 make: *** [debian/rules:8: clean] Error 25 It is planned to push boost_1.74 as the default version in Debian/Bullseye. [1] http://qa-logs.debian.net/2020/10/27-boost/boost/libzeep_3.0.5-2_unstable_boost.log Best regards Anton - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+6WXURHGdsYWRrQGRl Ymlhbi5vcmcACgkQ0+Fzg8+n/wYXFQ/6AobGTBmLGOayKBafvfY7JKMuOvQUt/CN 3x0Q1q9JKT3PrAiDupOILvGpU7kLVwXm+Xj7Y6jmOFmQXAIiejQINB5S3SMm3OW/ GJb2MkcbeAr/1gKnoRiXWGauFjBXT+RfHwKCB0qCRxaCcgd6wqN/sur9LiK1o9Jb yAxYOhsAuqU3zrmGbJ6H9WGzRsOAFjhWRDu9vvq9+XWwhCZ1msETk8J+ube6dI3G uYpkUgEUxf6dSLYAFki2vKtSX6TonmFwJ9Zn3uMer1OlTwOPGFfeKFP+Hvgd+Fx5 lwbGAh6RkoxM+9a+q+MSnIyhVoqMSYKWGbazen1SbJiQSR2tf8INYpryjd9wTYbK aFlazYitywFTlq4I9cu+vDuHzLP6/rV480+v
Bug#975446: libzeep: FTBFS against boost_1.74
Hi, The bug report is for libzeep version 5, but the logs show that an attempt was made to compile version 3. I'm quite sure that building libzeep version 5 with boost 1.74 will succeed, since I've been using it myself for several weeks now. regards, -maarten Op 22-11-2020 om 13:28 schreef Anton Gladky: Package: libzeep Version: 5.0.2-3 Severity: important Tags: ftbfs User: team+bo...@tracker.debian.org Usertags: boost174 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, it was discovered that your package failed to build against boost_1.74. Logs can be found here [1]. Most relevant part is probably this: dpkg-source: info: using options from libzeep-3.0.5/debian/source/options: --extend-diff-ignore=(^|/)(.vscode/.*|msvc|\.gitignore|\.travis\.yml|tests|zeep-test.*|webapp-test.cpp|doc/bin)$ fakeroot debian/rules clean dh clean dh_auto_clean make -j4 clean make[1]: Entering directory '/<>' rm -rf obj/* libzeep.a libzeep.so* zeep-test libzeep-3.0.5 libzeep-3.0.5.tgz cd doc; bjam clean Unable to load B2: could not find 'boost-build.jam' - --- Attempted search from '/<>/doc' up to the root at '/usr/bin/b2' Please consult the documentation at 'https://boostorg.github.io/build/'. make[1]: *** [makefile:122: clean] Error 1 make[1]: Leaving directory '/<>' dh_auto_clean: error: make -j4 clean returned exit code 2 make: *** [debian/rules:8: clean] Error 25 It is planned to push boost_1.74 as the default version in Debian/Bullseye. [1] http://qa-logs.debian.net/2020/10/27-boost/boost/libzeep_3.0.5-2_unstable_boost.log Best regards Anton - -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl+6WXURHGdsYWRrQGRl Ymlhbi5vcmcACgkQ0+Fzg8+n/wYXFQ/6AobGTBmLGOayKBafvfY7JKMuOvQUt/CN 3x0Q1q9JKT3PrAiDupOILvGpU7kLVwXm+Xj7Y6jmOFmQXAIiejQINB5S3SMm3OW/ GJb2MkcbeAr/1gKnoRiXWGauFjBXT+RfHwKCB0qCRxaCcgd6wqN/sur9LiK1o9Jb yAxYOhsAuqU3zrmGbJ6H9WGzRsOAFjhWRDu9vvq9+XWwhCZ1msETk8J+ube6dI3G uYpkUgEUxf6dSLYAFki2vKtSX6TonmFwJ9Zn3uMer1OlTwOPGFfeKFP+Hvgd+Fx5 lwbGAh6RkoxM+9a+q+MSnIyhVoqMSYKWGbazen1SbJiQSR2tf8INYpryjd9wTYbK aFlazYitywFTlq4I9cu+vDuHzLP6/rV480+v6ZRKgNLO8ciNu3i/vB/a8G23cdAu Bite4zw/29R5ekDUIvZcLLUSTVYfArKd1gMeRbVQFx9Y/AcFBC1/eZwqeiQFKmZv c1PwFhB9bl54jDqS/mb7c85uhzt2LEbEeLrzo69TaUxjo1/1vQCvZa2FMn5uZgBF aQwH4QSlL8Qh1zd3DW6DpQUzC4hg9TWFH/xIulFfuS46i2vD6UUDZYO/lBsw9Bod a5Sgqn6aeKSZs2StgSOf8HFF067rSOYbC3oaDO9/7xBmNe8FHjYLV27mFr6+Sotu OObqY7WdDP4= =ljID -END PGP SIGNATURE----- -- Maarten L. Hekkelman http://www.hekkelman.com/
Bug#975493: gitlab: Gitlab install script not working
Package: gitlab Version: 13.3.9-1+fto10+1 Severity: important Hi, Gitlab are not installing. I doesn't know the reason, but when I try to install it through apt-get upgrade (following debian/gitlab page for upgrading), that's not working. The log are the following: Precompiling assets... fatal: not a git repository (or any of the parent directories): .git fatal: not a git repository (or any of the parent directories): .git Attention: used pure ruby version of MurmurHash3 /usr/share/gitlab/lib/gitlab.rb:38: warning: already initialized constant Gitlab::COM_URL /usr/share/gitlab/lib/gitlab.rb:38: warning: previous definition of COM_URL was here /usr/share/gitlab/lib/gitlab.rb:39: warning: already initialized constant Gitlab::STAGING_COM_URL /usr/share/gitlab/lib/gitlab.rb:39: warning: previous definition of STAGING_COM_URL was here /usr/share/gitlab/lib/gitlab.rb:40: warning: already initialized constant Gitlab::APP_DIRS_PATTERN /usr/share/gitlab/lib/gitlab.rb:40: warning: previous definition of APP_DIRS_PATTERN was here /usr/share/gitlab/lib/gitlab.rb:41: warning: already initialized constant Gitlab::SUBDOMAIN_REGEX /usr/share/gitlab/lib/gitlab.rb:41: warning: previous definition of SUBDOMAIN_REGEX was here /usr/share/gitlab/lib/gitlab.rb:42: warning: already initialized constant Gitlab::VERSION /usr/share/gitlab/lib/gitlab.rb:42: warning: previous definition of VERSION was here /usr/share/gitlab/lib/gitlab.rb:43: warning: already initialized constant Gitlab::INSTALLATION_TYPE /usr/share/gitlab/lib/gitlab.rb:43: warning: previous definition of INSTALLATION_TYPE was here /usr/share/gitlab/lib/gitlab.rb:44: warning: already initialized constant Gitlab::HTTP_PROXY_ENV_VARS /usr/share/gitlab/lib/gitlab.rb:44: warning: previous definition of HTTP_PROXY_ENV_VARS was here yarn install v1.22.4 [1/4] Resolving packages... success Already up-to-date. $ node ./scripts/frontend/postinstall.js success Dependency postinstall check passed. Done in 0.74s. WARNING on line 297, column 11 of /usr/share/gitlab/app/assets/stylesheets/framework/common.scss: Compound selectors may no longer be extended. Consider `@extend .card, .card-body` instead. See http://bit.ly/ExtendCompound for details. WARNING on line 208, column 13 of /usr/share/gitlab/app/assets/stylesheets/framework/filters.scss: Compound selectors may no longer be extended. Consider `@extend .form-control, :hover` instead. See http://bit.ly/ExtendCompound for details. DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#292961 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#4b4ba3 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#1a3652 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#2261a1 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#0d4524 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#156b39 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#691a16 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead. https://sass-lang.com/documentation/Sass/Script/Functions.html#other_color_functions DEPRECATION WARNING on line 88 of /usr/share/gitlab/app/assets/stylesheets/framework/gitlab_theme.scss: The operation `#a62e21 plus 33` is deprecated and will be an error in future versions. Consider using Sass's color functions instead.
Bug#974973: ITP: libcifpp -- A library for creating and manipulating mmCIF and PDB files containing macro molecular structure information
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" * Package name: libcifpp Version : 1.0.0 Upstream Author : Maarten L. Hekkelman * URL : http://github.com/PDB-REDO/libcifpp * License : BSD-2-Clause Programming Lang: C++ Description : A library for creating and manipulating mmCIF and PDB files containing macro molecular structure information The structure of macro molecules is nowadays recorded in mmCIF files. Until recently however the ancient PDB file format was used by many programs but that format has since long been deprecated. This library contains code to read and write mmCIF files. It also contains validating code to check the integrity and validity of mmCIF files. As a bonus, this library is capable of importing and exporting PDB files which is not trivial. The code greatly benefits from the CCP4 distribution being available, but does not require it to work. The current DSSP in Debian needs to be replaced with a new version soon, this new version of DSSP will require libcifpp. The Debian Med team will take care of maintenance.
Bug#974895: ftp.debian.org: MRS should be updated to support the new libzeep library
Package: ftp.debian.org Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) MRS is an information retrieval system, used to index terabytes of text based databanks on a single machine. Mostly used in the medical and biological world. The version of MRS in currently in Debian is based on libzeep version 3. Libzeep was in fact a spin off project from MRS. I stopped development of MRS in 2012 when I switched to a new employer but I took libzeep with me. Since then, libzeep has evolved and changed a lot and now compatibility with MRS is broken. I've submitted the new version of libzeep into debian (it is currently in unstable) but now MRS no longer builds and so I request to remove it from Debian until it is updated. regards, -maarten
Bug#974016: mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed"
Hi Juhani, Bug #974074 is in fact a bug in MRS. However, the bug report does contain a useful observation, the usage of the various override_dh_auto_configure rules in libzeep is incorrect and no shared library is created. Now the question is, is a shared library really required? If so I will have to go back to the drawing board and redesign the makefiles in the upstream project to create proper shared libraries, including a version numbering scheme. regards, -maarten Op 11-11-2020 om 09:13 schreef Juhani Numminen: On Tue, 10 Nov 2020 23:03:57 +0100 Sebastian Ramacher wrote: Hi Marten On 2020-11-10 07:42:45 +0100, Maarten L. Hekkelman wrote: ... Sorry, long story. To make it short. - Keep mrc, no problem there - Upgrade libzeep to version 5 Thanks for the detailed explanation. The first two steps are almost done The current versions of mrc and libzeep should be able to migrate soon as their RC bugs have been fixed. ... Right, but one RC bug is not fixed yet: libzeep packages are missing the shared library altogether; the .so files are not there. For that we have bug #974074, and see gregor's message for suggested fix. It seems he is confident in the first diff of that mail, while the latter diff is more speculative. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974074#19 Regards, Juhani -- Maarten L. Hekkelman Cataloniëstraat 3 6663NJ Lent http://www.hekkelman.com/ +31 24 348 0192
Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526
Op 10-11-2020 om 16:21 schreef Andrey Rahmatullin: Running 7 test cases... started daemon at port 5923 terminate called after throwing an instance of 'boost::wrapexcept' what(): resolve: Host not found (authoritative) Looks like it tries to resolve something, and that usually implies Internet access, as otherwise you could just connect to localhost? Accessing the Internet is forbidden during building. The test case tried to resolve "127.0.0.1" as host. I've changed that to "localhost" since adding a flag for boost to only interpret the value as numeric is not easy to add to the code. I've seen hosts where localhost is mapped to some other IP address in the range 127.0.0.0/255 Could this be the case on the particular build machine where the test failed? Anyway, I assume that using localhost will be sufficient to fix this problem. We'll see that shorly. regards, -maarten
Bug#974016: mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed"
Hi Andreas, To avoid confusion, we're talking about three tools here: libzeep, mrc and mrs. mrc is a simple resource compiler, is now compatible and bug free, builds on all architectures and should be kept. I believe it is very useful, using it I can create downloadable, portable applications that need additional static data without the need for installer scripts. libzeep version 5 is the latest incarnation of a library I've been working on for 12 years now. It has evolved into a toolbox to build web applications in C++ inspired by the popular Java Spring framework and Thymeleaf template processor. It also contains a full XML and a JSON library. Using this library I could e.g. convert a pipeline to process genomics data into an interactive web application, the python scripts took up to 4 hours for each run, now you can do the same analysis in less than 5 seconds. I have a couple of applications based on libzeep that I would like to add to Debian, most of them tools used in crystallography and genomics research. But also a content management system. And then we have MRS. This is a retrieval system, a web application capable of indexing and then searching terabytes of text based databanks on a single machine. Mostly used in the medical and biological world. It is used e.g. on mini computers that are sent into Africa where internet access is limited, that way large databanks like EMBL are still available. But I stopped development in 2012 when I switched jobs. I continued development of libzeep on which MRS is based but someone else took over development of MRS. A year ago I did a consultancy job fixing MRS which basically came down to reverting most of the attempted 'improvements' after I left. Currently I'm working at the Netherlands Cancer Institute, here I write both software used in crystallography as well as a genomics analysis tool. Many of the crystallographic tools are moving into open source right now. We would have liked to include those in the CCP4 distribution, but unfortunately my code is way too new (C++17) to work in that environment. Next to that we would like to include our tools in Debian (DSSP already is, but that application needs an update), but if that won't work, I will set up a private repository to distribute our binaries. I know libzeep is not very popular, that's because I never bothered much to find an audience. But I can't live without it myself, a lot of my tools are based on it one way or another. Libzeep is also quite mature and has been used in many tools in a production environment for many years now. Sorry, long story. To make it short. - Keep mrc, no problem there - Upgrade libzeep to version 5 - Kick out mrs until it is upgraded to use libzeep 5 regards, -maarten Op 09-11-2020 om 20:49 schreef Andreas Tille: Hi Maarten, On Mon, Nov 09, 2020 at 07:22:30PM +0100, Maarten L. Hekkelman wrote: I'm sorry, but mrs as it is currently in Debian is not compatible with libzeep version 5. It needs a major rewrite. Libzeep is a spin off project of mrs and has evolved a lot since then. So either libzeep should be kept at version 3 or mrs should be removed. If mrs and libzeep are kept, I will not be able to release my other tools based on libzeep in Debian. You are the Uploader and the only competent person to decide. If I understood the issue correctly it came up right after mrc was added to the Build-Depends. Wouldn't it be an option to just de-couple both again. Upgrading mrs is of course the best option, but I won't have time to do that soon. So please draw a sensible decision. Libzeep was according to popcon[1] never installed by more than 10 users - currently the vote (active users) is at zero. Feel free to decided what *you* personally love to see in Debian (but decreasing a version number is usually not nice). Kind regards Andreas. [1] https://qa.debian.org/popcon.php?package=libzeep regards, -maarten Op 09-11-2020 om 16:19 schreef Niko Tyni: On Mon, Nov 09, 2020 at 09:17:25AM +0200, Juhani Numminen wrote: Source: mrs Version: 6.0.5+dfsg-8 Severity: serious Tags: ftbfs sid Justification: fails to build from source (but built successfully in the past) | Checking for libzeep...libzeep is not installed, either install the package libzeep-dev | or download libzeep from ftp://ftp.cmbi.ru.nl/pub/software/libzeep | and run configure again. | make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 2 Looks to me like libzeep-dev is broken because the build doesn't pass --enable-shared to ./configure. Probably the override_dh_auto_configure-arch and override_dh_auto_configure-indep targets in src:libzeep debian/rules are not effective because of the earlier override_dh_auto_configure target. But I didn't actually test any of this. Hope this helps, -- Maarten L. Hekkelman Cataloniëstraat 3 6663NJ Lent http://www.hekkelman.com/ -- Maarten L. Hekkelman Cataloniëstraat 3 6663NJ Lent http
Bug#974016: mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed"
I'm sorry, but mrs as it is currently in Debian is not compatible with libzeep version 5. It needs a major rewrite. Libzeep is a spin off project of mrs and has evolved a lot since then. So either libzeep should be kept at version 3 or mrs should be removed. If mrs and libzeep are kept, I will not be able to release my other tools based on libzeep in Debian. Upgrading mrs is of course the best option, but I won't have time to do that soon. regards, -maarten Op 09-11-2020 om 16:19 schreef Niko Tyni: On Mon, Nov 09, 2020 at 09:17:25AM +0200, Juhani Numminen wrote: Source: mrs Version: 6.0.5+dfsg-8 Severity: serious Tags: ftbfs sid Justification: fails to build from source (but built successfully in the past) | Checking for libzeep...libzeep is not installed, either install the package libzeep-dev | or download libzeep from ftp://ftp.cmbi.ru.nl/pub/software/libzeep | and run configure again. | make[1]: *** [debian/rules:15: override_dh_auto_configure] Error 2 Looks to me like libzeep-dev is broken because the build doesn't pass --enable-shared to ./configure. Probably the override_dh_auto_configure-arch and override_dh_auto_configure-indep targets in src:libzeep debian/rules are not effective because of the earlier override_dh_auto_configure target. But I didn't actually test any of this. Hope this helps, -- Maarten L. Hekkelman Cataloniëstraat 3 6663NJ Lent http://www.hekkelman.com/
Bug#971405: obs-studio feature request: build with caption support
Package: obs-studio Version: 25.0.8 Severity: wishlist Currently obs-studio is built with caption support disabled as that used to fail to compile on linux but that was now fixed in OBS a while ago https://github.com/obsproject/obs-studio/pull/2099 and works without problems now. It would be great if it could now be built with -DBUILD_CAPTIONS=ON like is the default on all their official releases on other platforms to allow scripts and plugins to output closed captions to streams. Thank you!
Bug#970429: claws-mail-smime-plugin: Error loading claws-mail-smime-plugin on debian/bullseye
Package: claws-mail-smime-plugin Version: 3.17.6-1 Severity: normal X-Debbugs-Cc: de...@public-files.de Hi, Upon loading the claws-mail-smime-plugin, the following error occurs, hence the plugin is not loadable. The following error occurred while loading smime.so: /usr/lib/x86_64-linux-gnu/claws-mail/plugins/smime.so: undefined symbol: prefs_gpg_auto_check_signatures A workaround is to load pgpmime (also loads pgpcore) which seem to include the missing symbol. Loading smime afterwards works. Best wishes, Martin -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages claws-mail-smime-plugin depends on: ii claws-mail 3.17.6-1 ii claws-mail-pgpmime [claws-mail-pgpcore] 3.17.6-1 ii gpgsm2.2.20-1 ii libc62.31-3 ii libglib2.0-0 2.66.0-1 ii libgpg-error01.38-2 ii libgpgme11 1.14.0-1 claws-mail-smime-plugin recommends no packages. claws-mail-smime-plugin suggests no packages. -- no debconf information
Bug#970087: ITP: mrc -- resource compiler to store data in ELF object files
Package: wnpp Severity: wishlist Owner: "Maarten L. Hekkelman" * Package name: mrc Version : 1.2.2 Upstream Author : Maarten L. Hekkelman * URL : http://github.com/mhekkel/mrc * License : BSD-2-Clause-FreeBSD Programming Lang: C++ Description : resource compiler to store data in ELF object files Many applications come with supplementary data. This data is usually stored on disk as regular files. The disadvantage of this procedure is that an application cannot simply be copied to another location or computer and expected to function properly. Resources are a way to overcome this problem by including all data inside the executable file. The mrc resource compiler can create object files containing both the data and an index. This data can then be accessed from within an application using C++ classes. A header file to include in your C++ application is provided. As a resource in mrc of course. I'm the author of libzeep, a C++ based web application framework and in combination with mrc I can create web based application with a C++ backend, all combined in a single executable that's easily distributable. Libzeep is already sponsored by the Med team.
Bug#966218: marked as done (firmware: failed to load iwl-debug-yoyo.bin (-2))
control: reopen -1 control: found -1 5.8.7-1 $ uname -a Linux foo 5.8.0-1-amd64 #1 SMP Debian 5.8.7-1 (2020-09-05) x86_64 GNU/Linux $ journalctl -k -g iwl-debug-yoyo -- Logs begin at Mon 2020-08-03 07:03:27 EDT, end at Wed 2020-09-09 16:08:47 EDT. -- Sep 09 15:53:32 foo kernel: iwlwifi :03:00.0: firmware: failed to load iwl-debug-yoyo.bin (-2)
Bug#966218: firmware: failed to load iwl-debug-yoyo.bin (-2)
Control: notfound -1 20200421-1 Control: reassign -1 src:linux Control: found -1 5.5.13-1 Control: found -1 5.7.17-1 Control: forwarded -1 https://lore.kernel.org/linux-wireless/20200625165210.14904-1-...@kernel.org/ Control: severity -1 minor Control: tags -1 + patch pending upstream fixed-upstream -- An upstream patch [0] that suppresses this (harmless) error message was merged in v5.9-rc1 [1] and should be available in 5.9 and later kernels. As a "workaround" (if the error message bothers you), you may set the iwlwifi module's "enable_ini" parameter to false (e.g., "N"). This will disable the (attempted) loading of the "iwl-debug-yoyo.bin" file -- which fails, obviously, causing this error to be generated. [0]: https://patchwork.kernel.org/patch/11625759/ [1]: https://github.com/torvalds/linux/commit/3f4600d
Bug#967960: navit or navit-data does not include the layout xml files required to display maps.
Package: navit Version: 0.5.4+dfsg.1-4 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Downloading maps for navit from the navit map site and editing navit.xml didn't let maps be displayed * What exactly did you do (or not do) that was effective (or ineffective)? I downloaded a layout file from github https://github.com/navit-gps/navit/blob/trunk/navit/navit_layout_car_android_shipped.xml and edited the navit.xml to load it. e.g. * What was the outcome of this action? The map was able to be displayed * What outcome did you expect instead? the layouts should be packaged in navit-data and loaded automatically. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: arm64 (aarch64) Kernel: Linux 5.7-pinephone (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_CRAP Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages navit depends on: ii libc6 2.31-2 ii libdbus-1-3 1.12.20-1 ii libdbus-glib-1-20.110-5 ii libfontconfig1 2.13.1-4.2 ii libfreetype62.10.2+dfsg-3 ii libfribidi0 1.0.8-2 ii libgarmin0 0~svn320-6 ii libglib2.0-02.64.4-1 ii libgps263.20-12 ii libspeechd2 0.9.1-5 ii navit-data 0.5.4+dfsg.1-4 ii navit-gui-internal 0.5.4+dfsg.1-4 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages navit recommends: ii gpsd 3.20-12 Versions of packages navit suggests: pn maptool -- no debconf information
Bug#895237: Information
I am trying to get information to this account Karen