Bug#950614: libqt5core5a conflicts with libqtcore4
Package: libqt5core5a Version: 5.12.5+dfsg-8 Severity: normal The latest version of libqt5core5a breaks libqtcore4 (< 4:4.8.7+dfsg-20~), which is any libqtcore4 version currently available in unstable. Is this intentional? This makes libqt5core5a uninstallable for me. I have several programs which still depend on libqtcore4. I also still develop on qt4.
Bug#945490: gs always fails with "Permission denied"
Package: pstoedit Version: 3.74-1+b1 Severity: important Tried pstoedit for the first time today, but I couldn't get it to work. After a few tests, I noticed it would fail to run even when converting a dummy pdf (saved with inkscape) to a ps. The following command: $ pstoedit lay1.pdf lay1.ps Results in === pstoedit: version 3.74 / DLL interface 108 (built: Aug 24 2019 - release build - g++ 9.2.1 20190821 - 64-bit) : Copyright (C) 1993 - 2019 Wolfgang Glunz No explicit output format specified - using plot-ps as derived from suffix of output file *** WARNING - you have selected SAFER, indicating you want Ghostscript to execute in a safer environment, but at the same time have selected DELAYBIND. Unless you use this option with care (and specifically, remember to call .bindnow) it is possible that malicious code may be able to evade the limited security offered by the SAFER option. *** WARNING - you have selected SAFER, indicating you want Ghostscript to execute in a safer environment, but at the same time have selected WRITESYSTEMDICT. Unless you use this option with care and specifically, remember to execute code like: "systemdict readonly pop" it is possible that malicious code may be able to evade the limited security offered by the SAFER option. Error: /invalidfileaccess in --run-- Operand stack: (lay1.pdf) (r) Execution stack: %interp_exit .runexec2 --nostringval-- run --nostringval-- 2 %stopped_push --nostringval-- run run false 1 %stopped_push 1989 1 3 %oparray_pop 1988 1 3 %oparray_pop 1976 1 3 %oparray_pop 1833 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- run --nostringval-- 2 %stopped_push --nostringval-- 1989 1 3 %oparray_pop run Dictionary stack: --dict:730/1684(ro)(G)-- --dict:0/20(G)-- --dict:303/450(L)-- Current allocation mode is local Last OS error: Permission denied Current file position is 89272 GPL Ghostscript 9.50: Unrecoverable error, exit code 1 PostScript/PDF Interpreter finished. Return status 256 executed command : gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS "/tmp/psinD1zLI9" The interpreter seems to have failed, cannot proceed ! === "lay1.ps" is created as zero file. It seems that gs doesn't have enough permissions to read the input (?). I cannot it to run even using stdin/out only. But if I explicitly disable gs "SAFER" with $ pstoedit -psarg '-dNOSAFER' in out then I can convert documents as expected. I'm filing this as important, since I don't think explicitly disabling the gs sandbox is the right fix. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-rt-amd64 (SMP w/8 CPU cores; 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pstoedit depends on: ii ghostscript 9.50~dfsg-2 ii libc62.29-3 ii libpstoedit0c2a 3.74-1+b1 ii libstdc++6 9.2.1-19 pstoedit recommends no packages. Versions of packages pstoedit suggests: pn xfig | ivtools-bin | tgif | transfig
Bug#943945: doc-base error during install
Package: python-sympy-doc Version: 1.4-1 Severity: normal Processing 3 changed doc-base files... Error in `/usr/share/doc-base/sympy', line 8: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-3-rt-amd64 (SMP w/8 CPU cores; 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) python-sympy-doc depends on no packages. python-sympy-doc recommends no packages. Versions of packages python-sympy-doc suggests: pn python-sympy
Bug#910613: Unecessary dependency on python3-tk
Package: python3-seaborn Version: 0.9.0-1 Followup-For: Bug #910613 Still true as of 0.9.0-2. seaborn does *not* need tk.
Bug#942519: Please rebuild for exiv2-27
On Thu, Oct 17 2019, Jason Crain wrote: > On 2019-10-17, Yuri D'Elia wrote: >> This has been fixed in libexiv2-27. Would it be possible to rebuild >> against the newer version? Thanks. > > exiv2 0.27 is only in experimental. Are you asking me to upload a new > version of gexiv2 to experimental? Ah! My bad, I didn't realize I pinned it from there. Sorry for this. I would still be happy about an upload to experimental though.
Bug#942519: Please rebuild for exiv2-27
Package: libgexiv2-2 Version: 0.10.9-1 Severity: normal libgexiv2 links against libexiv2-14 which has several bugs handling temporary files (see #932627). This is indirectly causing gimp's "export" to leave stray temporary files around (https://gitlab.gnome.org/GNOME/gimp/issues/3662). This has been fixed in libexiv2-27. Would it be possible to rebuild against the newer version? Thanks.
Bug#940815: zathura: Mouse wheel zoom inconsistent with girara >= 0.3.3
Package: zathura Version: 0.4.4-1 Followup-For: Bug #940815 I also find the zoom direction to be inverted. I tried to remap Button4/Button5, but no maps involving Button4/5 have effect: map Button4 zoom in map zoom in It seems that the mouse wheel behavior cannot be overridden.
Bug#935173: audacity graphical windows fail to update properly
On Sun, Sep 22 2019, Klaumi Klingsporn wrote: > This bug-message I get on the console too, so it may be > related to the problems but doesn't seem to cause them. Ok -- wow, I think I've found the issue. I ran under a different system, and it seems that setting: export GTK_IM_MODULE=xim is causing the issue (!). If I unset this, then audacity works. Could you confirm this?
Bug#935173: audacity graphical windows fail to update properly
On Sun, Sep 22 2019, Klaumi Klingsporn wrote: > But I remember that I had similar problems with a > self-compiled earlier 2.3-version of audacity. I had to > move the configuration-directory (~/.audacity-data) out of > the way and to choose the classic-theme to make it work. > > Maybe this helps? I tried zapping ~/.audacity-data, but I have the same issue. Some widgets do not repaint properly, but the main issue is that audio tracks only seem to redraw when resizing the main window. I rebuilt audacity from git earlier today, but it still doesn't repaint the tracks (for instance, while playing, zooming, etc). The only thing I see is errors on the console: *** BUG *** In pixman_region32_init_rect: Invalid rectangle passed Set a breakpoint on '_pixman_log_error' to debug but I'm not sure if they're related or not.
Bug#935173: audacity graphical windows fail to update properly
Package: audacity Version: 2.3.2-2 Followup-For: Bug #935173 "Very difficult" is an understatement. audacity 2.3.2 is basically unusable as it is :(
Bug#940710: Fails to load pkcs8_key_parser module
Package: iwd Version: 0.21-1 Severity: normal iwd includes /usr/lib/modules-load.d/pkcs8.conf to load pkcs8_key_parser when available. This however causes an error message during startup in my case, which I'd like to silence. I would recommend moving the file to /etc/modules-load.d, possibly using ucf, so that I can modify/remove the file and have the change persist across package upgrades. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores) 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages iwd depends on: ii libc6 2.29-1 ii libreadline8 8.0-3 iwd recommends no packages. iwd suggests no packages.
Bug#940483: imgproc4.1 depends on unavailable libopenexr23
Package: libopencv-imgcodecs4.1 Severity: normal libopencv-imgcodecs4.1 on experimental probably needs a rebuild. It currently depends on libopenexr23, which is unavaiable. The current version on sid is libopenexr24.
Bug#939571: Fails to import
Package: python3-pyqtgraph Version: 0.10.0-4 Severity: important Version 0.10.0-4 fails to import: import pyqtgraph Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/pyqtgraph/__init__.py", line 210, in from .graphicsItems.GraphicsLayout import * File "/usr/lib/python3/dist-packages/pyqtgraph/graphicsItems/GraphicsLayout.py", line 6, in from .PlotItem import PlotItem File "/usr/lib/python3/dist-packages/pyqtgraph/graphicsItems/PlotItem/__init__.py", line 1, in from .PlotItem import PlotItem File "/usr/lib/python3/dist-packages/pyqtgraph/graphicsItems/PlotItem/PlotItem.py", line 9, in from ...widgets.FileDialog import FileDialog ModuleNotFoundError: No module named 'pyqtgraph.widgets'
Bug#939474: New version 1.5.2 available
Package: libzip4 Version: 1.5.1-4 Severity: normal Upstream released 1.5.2 in 2019-03-12 which fixes a bug with encryption. It would be nice if the package would be updated. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-rt-amd64 (SMP w/8 CPU cores; 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libzip4 depends on: ii libbz2-1.0 1.0.6-9.2 ii libc6 2.29-0experimental1 ii libssl1.1 1.1.1c-1 ii zlib1g 1:1.2.11.dfsg-1+b1 libzip4 recommends no packages. libzip4 suggests no packages.
Bug#933840: doc-base installation errors
Package: nodejs-doc Version: 12.7.0~dfsg-1 Severity: normal Processing 2 changed doc-base files... Error in `/usr/share/doc-base/nodejs-api', line 9: all `Format' sections are invalid. Note: `install-docs --verbose --check file_name' may give more details about the above error.
Bug#932627: Leaves stray temporary files around
Package: libexiv2-14 Version: 0.25-4 Severity: normal There's a bug in libexiv2-14 that leaves stray temporary files in the dirctory where files are saved. This can be reproduced with Gimp 2.10.8 which uses libexiv2 indirectly though libgexiv by doing an export to any file with Exif data (jpg/png) and noticing that a second, truncated file with a random number appened is created in the same directory. I'm not sure if this bug was introduced by upstream or one of the fixes applied in debian. The bug is fixed in the version uploaded in experimental (0.26-1), which does mention incorrect temporary file leakage in the upstream changelog. I would also point out that a newer upstream (0.27.1) is available as well, and I verified that it also doesn't contain the issue. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-rt-amd64 (SMP w/8 CPU cores; 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libexiv2-14:amd64 depends on: ii libc6 2.28-10 ii libexpat1 2.2.7-1 ii libgcc1 1:9.1.0-10 ii libstdc++6 9.1.0-10 ii zlib1g 1:1.2.11.dfsg-1 libexiv2-14:amd64 recommends no packages. Versions of packages libexiv2-14:amd64 suggests: ii exiv2 0.26-1
Bug#931717: samba: CUPS printing fails with NT_STATUS_LOGON_FAILURE in 4.9.11+dfsg-1
Package: smbclient Version: 2:4.9.11+dfsg-1 Followup-For: Bug #931717 Here's the thing: if you replace /usr/lib/cups/backend/smb with a shell script that simply calls smbspool: #!/bin/sh exec /usr/bin/smbspool "$@" it works. I wanted to debug if DEVICE_URI was set correctly, and it is. The documentation of smbspool mentions that it tries to use ARGV[0] if it starts with a smb:// prefix. I assume cups sets ARGV[0] to the internal device_uri, which strips the username/password (as seen in the web interface) and smbspool will now take this value instead of DEVICE_URI. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-rt-amd64 (SMP w/8 CPU cores; 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smbclient depends on: ii dpkg 1.19.7 ii libarchive13 3.3.3-4 ii libbsd0 0.9.1-2 ii libc6 2.28-10 ii libpopt0 1.16-12 ii libreadline8 8.0-2 ii libsmbclient 2:4.9.11+dfsg-1 ii libtalloc22.1.14-2 ii libtevent00.9.37-1 ii samba-common 2:4.9.11+dfsg-1 ii samba-libs2:4.9.11+dfsg-1 smbclient recommends no packages. Versions of packages smbclient suggests: ii cifs-utils 2:6.8-2 pn heimdal-clients
Bug#932291: New upstream 2.10.12 available
Package: gimp Version: 2.10.8-2 Severity: wishlist Dear maintainer, GIMP 2.10.12 is available (two minor releases above the current package). Thanks
Bug#914660: entr FTCBFS: builds for the wrong architecture
On Fri, Jun 07 2019, Otto Kekäläinen wrote: > Hello! > > Sorry for the long delay in replying. This one completely slipped under by radar. Thanks Otto for pinging me. > i looked at the patch but I am not sure if I understand it fully. > > Upstream is very responsive so I suggest you send a pull request at > https://bitbucket.org/eradman/entr/pull-requests/ for the parts that > are upstreamable and for the rest a merge request is welcome at > https://salsa.debian.org/debian/entr/merge_requests It looks clean and very sensible to me. Eric was always very keen in accepting suggestions, if you could create and issue or PR it would be great, so that we could simply use the upstream source directly. I also agree on the solution to simply bypass configure with the configure override. The upstream's solution is very simplistic, and as long as all it does is makefile selection than it's even cleaner.
Bug#923151: "unknown reason 'attempt-reconnect'" when using openconnect 8.02-1
Package: vpnc-scripts Version: 0.1~git20180227-1 Severity: normal When using openconnect 8.02-1 and network connection is lost, the reconnection attempt shows this error: CSTP Dead Peer Detection detected dead peer! unknown reason 'attempt-reconnect'. Maybe vpnc-script is out of date Script '/usr/share/vpnc-scripts/vpnc-script' returned error 1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.20.0-trunk-amd64 (SMP w/8 CPU cores) 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.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vpnc-scripts depends on: ii iproute2 4.20.0-2 vpnc-scripts recommends no packages. Versions of packages vpnc-scripts suggests: pn dnsmasq ii openssh-server 1:7.9p1-6 pn resolvconf
Bug#919903: Package wxWidgets 3.1
Package: wx-common Version: 3.0.4+dfsg-8 Severity: wishlist It would be helpful to have a package for the 3.1.* release (currently 3.1.2) of wxWidgets for development purposes, even if that just targets experimental. Although still considered "development" and not 100% compatible with 3.0, wx 3.1 includes a plethora of bug fixes that forced me to upgrade for development. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wx-common depends on: ii libc6 2.28-5 ii libgcc1 1:8.2.0-14 ii libstdc++68.2.0-14 ii libwxbase3.0-0v5 3.0.4+dfsg-8 Versions of packages wx-common recommends: ii zip 3.0-11+b1 wx-common suggests no packages.
Bug#918050: iv doesn't do anything
On Thu, Jan 03 2019, Matteo F. Vescovi wrote: >> Nothing else is displayed/shown. >> Admittedly, I never cared enough to report. > > It works just fine here. See attached image. > Please, provide more context to address the issue. I really have no idea here of any possible cause. Is iv qt or gtk? qt with a glib main loop? If you have a couple of ideas I can try to narrow down the issue, otherwise I really don't care enough to debug it. I'm just reporting the finding here. It used to work, but not anymore. I tried on a new user (to ensure there is _no_ customization), but it does the same. This is debian unstable, without any DE (just openbox).
Bug#918050: iv doesn't do anything
Package: openimageio-tools Version: 2.0.3~dfsg0-3 Severity: normal I used "iv" a couple of times in the past, mostly out of curiosity. I tried again today since I saw upstream' bug #318 should be fixed (bad gamma handling). However, in the last several releases (afaik, since at least 6 months) it doesn't display any UI when started. % iv -F IMG_20181228_194324.jpg (iv:10030): GLib-GObject-WARNING **: 20:41:45.722: cannot register existing type 'GtkWidget' (iv:10030): GLib-GObject-CRITICAL **: 20:41:45.722: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed (iv:10030): GLib-GObject-WARNING **: 20:41:45.722: cannot register existing type 'GtkBuildable' (iv:10030): GLib-GObject-CRITICAL **: 20:41:45.722: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed (iv:10030): GLib-CRITICAL **: 20:41:45.722: g_once_init_leave: assertion 'result != 0' failed (iv:10030): GLib-GObject-CRITICAL **: 20:41:45.722: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed (iv:10030): GLib-GObject-CRITICAL **: 20:41:45.722: g_type_register_static: assertion 'parent_type > 0' failed Nothing else is displayed/shown. Admittedly, I never cared enough to report. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openimageio-tools depends on: ii libatomic1 8.2.0-13 ii libavcodec58 10:4.1-dmo3 ii libavformat58 10:4.1-dmo3 ii libavutil5610:4.1-dmo3 ii libboost-atomic1.67.0 1.67.0-11 ii libboost-chrono1.67.0 1.67.0-11 ii libboost-date-time1.67.0 1.67.0-11 ii libboost-filesystem1.67.0 1.67.0-11 ii libboost-system1.67.0 1.67.0-11 ii libboost-thread1.67.0 1.67.0-11 ii libc6 2.28-4 ii libdcmtk12 3.6.2-3+b2 ii libfreetype6 2.9.1-3 ii libgcc11:8.2.0-13 ii libgif75.1.4-3 ii libgl1 1.1.0-1 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii libilmbase23 2.2.1-2 ii libjpeg62-turbo1:1.5.2-2+b1 ii libopencolorio1v5 1.1.0~dfsg0-3 ii libopencv-core3.2 3.2.0+dfsg-5 ii libopencv-imgproc3.2 3.2.0+dfsg-5 ii libopencv-videoio3.2 3.2.0+dfsg-5 ii libopenexr23 2.2.1-4 ii libopenimageio2.0 2.0.3~dfsg0-3 ii libopenjp2-7 2.3.0-1.1 ii libopenvdb5.2 5.2.0-5 ii libpng16-161.6.36-2 ii libqt5core5a 5.11.3+dfsg-2 ii libqt5gui5 5.11.3+dfsg-2 ii libqt5opengl5 5.11.3+dfsg-2 ii libqt5widgets5 5.11.3+dfsg-2 ii libraw19 0.19.2-1 ii libstdc++6 8.2.0-13 ii libswscale510:4.1-dmo3 ii libtbb22018~U6-4 ii libtiff5 4.0.10-3 ii libwebp6 0.6.1-2 ii zlib1g 1:1.2.11.dfsg-1 openimageio-tools recommends no packages. openimageio-tools suggests no packages.
Bug#916159: Shouldn't depend on gfortran
Package: libopenmpi-dev Version: 3.1.3-4 Severity: normal I feel libopenmpi-dev shouldn't depend on a compiler directly. libopenmpi-dev, specifically, doesn't require gfortran8 to be usable. After discussion with the maintainer, it seems that the package ships with version-specific precompiled headers. Depending on the compiler seems the wrong way to ensure the headers compatible. A better solution would be a Breaks against != gfortran-mod-[version]. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-trunk-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopenmpi-dev:amd64 depends on: ii gfortran-8 [gfortran-mod-15] 8.2.0-12 ii libhwloc-dev 1.11.11-2 ii libibverbs-dev21.0-1 ii libopenmpi3 3.1.3-4 ii openmpi-bin 3.1.3-4 ii openmpi-common3.1.3-4 Versions of packages libopenmpi-dev:amd64 recommends: pn libcoarrays-openmpi-dev Versions of packages libopenmpi-dev:amd64 suggests: ii openmpi-doc 3.1.3-4
Bug#904611: Crash on "Automatic reconstruction" if no GPU is supported
On Thu, Nov 29 2018, Gürkan Myczko wrote: > Does this also happen with 3.5? > Or the 3.6 available at: http://phd-sid.ethz.ch/debian/colmap/cm36/ ? I didn't explicitly try your build, but I've rebuilt colmap 3.6 from source a while ago (since I've also reported the bug upstream) and it doesn't "crash" anymore. However, the GUI is left in a broken state. The progress window doesn't respond anymore after a bogus completion message. If you manually close it, the log is still visible and shows that SiftGPU is not supported. It could be better, but at least the error message is visible, which allows someone to continue.
Bug#914750: High cpu usage
On Mon, Nov 26 2018, Bill Allombert wrote: > On my laptop with 49 days uptime (w/ lot of suspend-to-disk), > consolation only used 30m and I always use the console. Random question: could it be that it's due to the fact that I barely use the console at all? > What kind of pointing devices do you have ? This is a lenovo yoga 3rd gen. Integrated touchpad, touchscreen (that I disabled via `xinput float`), the red-finger-joystick thingy, it has a built-in wacom digitizer (that I do use - but not today) and generally an additional usb mouse plugged too. So... yeah. There are some pointing devices. > We would need to use some profiling to see how the time is spend. > (If it is spend in libinput, then this might not be fixable in > consolation). Any specific tool you want me to run? gprof with default arguments would be fine?
Bug#914750: High cpu usage
Package: consolation Severity: normal Version: 0.0.6-2 I've been running consolation for quite a while but I noticed recently it accumulates a considerable amount of CPU time over the course of a day. On a system with a ~2 hours uptime, sorting by cpu time, I have Xorg (40m), pulseaudio (20m) and consolation (15m)! which is taking more CPU time than my window manager or systemd... And I never switched to the console since boot. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-rc7-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages consolation depends on: ii libc6 2.27-8 ii libevdev2 1.6.0+dfsg-1 ii libinput10 1.12.1-1 ii libudev1239-13 ii lsb-base9.20170808 consolation recommends no packages. consolation suggests no packages.
Bug#913893: Newer version 0.10.0 available
Package: ripgrep Version: 0.9.0-6 Severity: wishlist Dear maintainer, there's a newer upstream version available: 0.10.0 It would be nice to have an updated package, thanks! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ripgrep depends on: ii libc62.27-8 ii libgcc1 1:8.2.0-9 ripgrep recommends no packages. ripgrep suggests no packages.
Bug#913330: New upstream 3.4.3 available
Package: libopencv-dev Version: 3.3.0+dfsg-1~exp0+b4 Severity: normal Dear maintainer, the newest available upstream is at version 3.4.3. The current version available on unstable is 3.2.0 which is two years old. 3.3.0 on experimental is one year old. There are multiple vulnerabilities published for both. It would be nice to update to a current version of opencv. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libopencv-dev depends on: ii libc6 2.27-8 ii libgcc1 1:8.2.0-9 ii libopencv-calib3d-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-calib3d3.3 3.3.0+dfsg-1~exp0+b4 ii libopencv-contrib-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-contrib3.3 3.3.0+dfsg-1~exp0+b4 ii libopencv-core-dev3.3.0+dfsg-1~exp0+b4 ii libopencv-core3.3 3.3.0+dfsg-1~exp0+b4 ii libopencv-features2d-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-features2d3.3 3.3.0+dfsg-1~exp0+b4 ii libopencv-flann-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-flann3.33.3.0+dfsg-1~exp0+b4 ii libopencv-highgui-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-highgui3.3 3.3.0+dfsg-1~exp0+b4 ii libopencv-imgcodecs-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-imgcodecs3.33.3.0+dfsg-1~exp0+b4 ii libopencv-imgproc-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-imgproc3.3 3.3.0+dfsg-1~exp0+b4 ii libopencv-ml-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-objdetect-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-objdetect3.33.3.0+dfsg-1~exp0+b4 ii libopencv-photo-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-shape-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-stitching-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-superres-dev3.3.0+dfsg-1~exp0+b4 ii libopencv-ts-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-video-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-videoio-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-videoio3.3 3.3.0+dfsg-1~exp0+b4 ii libopencv-videostab-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv-viz-dev 3.3.0+dfsg-1~exp0+b4 ii libopencv3.3-java 3.3.0+dfsg-1~exp0 ii libstdc++68.2.0-9 ii libtbb2 2017~U7-8 ii pkg-config0.29-4+b1 Versions of packages libopencv-dev recommends: ii opencv-data 3.3.0+dfsg-1~exp0 Versions of packages libopencv-dev suggests: ii opencv-doc 3.3.0+dfsg-1~exp0
Bug#912469: Spourious blank line without parameters
Package: members Version: 20080128-5+nmu1+b1 Severity: minor Running "members" without parameters shows a spourious blank line before "Usage:". -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages members depends on: ii libc6 2.27-8 ii libgcc1 1:8.2.0-9 ii libstdc++6 8.2.0-9 members recommends no packages. members suggests no packages.
Bug#809321: systemd-rfkill state save/restore issues
On Mon, Oct 29 2018, Michael Biebl wrote: >> TBH, I'm not quite sure what your particular problem is. I wanted to prevent systemd-rfkill to restore the state on boot without a kernel parameter. I ended-up masking the systemd-rfkill.service, which essentially does what I want. We can close this.
Bug#911870: Should not depend on libjs-sphinxdoc
Package: python-configparser Version: 3.5.0b2-1 Severity: normal I guess python-configparser depends on libjs-sphinxdoc because the documentation makes use of it. I cound understand a direct dependency if this would be done in a -doc package, but in this case I feel the dependency should be downgraded to a "Suggests". There's no requirement or improvement of configobj if libjs-sphinxdoc is installed when using the module itself. Thanks -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-rc7-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-configparser depends on: ii libjs-sphinxdoc 1.7.9-1 ii python 2.7.15-3 python-configparser recommends no packages. python-configparser suggests no packages.
Bug#911614: Module Mail::SPF::BlackMagic should be included
On Tue, Oct 23 2018, Scott Kitterman wrote: >>I had to install the "spfquery" package to actually debug some domain >>rules. > > There is also an spfquery provided by spf-tools-python. Thanks for pointing this out, but it doesn't seem to allow tweaking as much as "spfquery" (from spfquery/libspf2). I needed basic stuff like "override" (in order to test the rules) and "max-interactive-terms" to spot some issues in a system with a broken spf policy that was trying to deliver to my system. It seems that only spfquery.libspf2 can be used for such purposes.
Bug#911614: Module Mail::SPF::BlackMagic should be included
On Mon, Oct 22 2018, gregor herrmann wrote: > You can easily sub-class Mail::SPF::Server and the > Mail::SPF::Result class collection in order to extend or modify > their behavior. The hypothetical Mail::SPF::BlackMagic package was > once supposed to make use of this. > > also doesn't increase the hopes. Hah :/ > So unless someone finds Mail::SPF::BlackMagic somewhere, we won't be > able to package/ship it. > Otherwise it might make sense to patch out the references to > ::BlackMagic from the existing code … Basically all the debugging functionality listed in the spfquery manpage is thus actually unimplemented!?.. That's quite a bit of documentation for an hypothetical module! I had to install the "spfquery" package to actually debug some domain rules.
Bug#907518: New libssl1.1 1.1.1~~pre9-1 in unstable breaks connecting to some wifi networks
Package: wpasupplicant Version: 2:2.7~git20181004+1dd66fc-1 Followup-For: Bug #907518 wpasupplicant should accept a tls MinVersion parameter to be specified per-network. Nobody wants to adjust the global setting just to connect to an outdated system. As pointed out, I also spotted this while trying to connect to eduroam. I raised the issue to the local admin, but meanwhile I had no choice but to lower the MinVersion for everything else in the system too. With per-ssid settings, I could actually set even stricter requirements for my own networks, which would be a big plus. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-rc7-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wpasupplicant depends on: ii adduser 3.118 ii libc6 2.27-6 ii libdbus-1-3 1.12.10-1 ii libnl-3-200 3.4.0-1 ii libnl-genl-3-200 3.4.0-1 ii libpcsclite1 1.8.24-1 ii libreadline7 7.0-5 ii libssl1.1 1.1.1-1 ii lsb-base 9.20170808 wpasupplicant recommends no packages. Versions of packages wpasupplicant suggests: pn libengine-pkcs11-openssl ii wpagui2:2.6-18
Bug#892841: Opening a file with O_CREAT fails
Package: smbnetfs Version: 0.6.1-1 Followup-For: Bug #892841 The patch provided by Alexander fixes the issue in my case. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-rc7-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smbnetfs depends on: ii libc6 2.27-6 ii libfuse2 2.9.8-2 ii libglib2.0-0 2.58.1-2 ii libsecret-1-0 0.18.6-3 ii libsmbclient 2:4.8.5+dfsg-1 Versions of packages smbnetfs recommends: ii fuse 2.9.8-2 smbnetfs suggests no packages.
Bug#910613: Unecessary dependency on python3-tk
Package: python3-seaborn Version: 0.8.0-1 Severity: normal NMU version 0.8.0-1.1 add a Depends: python3-tk, however this dependency shouldn't be there. I fought hard to remove it in the first place. If you follow the bug report in #896401 and #896003, the dependency is triggered when using matplotlib. matplotlib *already* recommends python3-tk. That's already correct and enough. matplotlib doesn't *depend* on it because the tk backend is *not* required for matplotlib to work. matplotlib can work with agg, Qt or cairo. The python3-tk dependency is pulling extra useless dependencies on headless systems. Please remove the extra dependency. Thanks -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-seaborn depends on: ii python3 3.6.6-1 ii python3-matplotlib 2.2.2-4+b1 ii python3-numpy 1:1.14.5-1+b1 ii python3-pandas 0.23.3-1 ii python3-scipy 1.1.0-1+b1 Versions of packages python3-seaborn recommends: pn python3-bs4 ii python3-patsy 0.4.1+git34-ga5b54c2-1 python3-seaborn suggests no packages.
Bug#910116: Wrong dependencies
Package: screenkey Severity: minor python-xlib is not required by screenkey. You must depend on libx11-6 explicitly.
Bug#901774: [pkg-uWSGI-devel] Bug#901774: Crash on SIGQUIT with plugin-python3
On Sun, Sep 30 2018, Jonas Smedegaard wrote: > Quoting wavexx (2018-07-12 11:32:38) >> This is still true for 2.0.17. uwsgi-plugin-python3 cannot be >> gracefully shutdown: > > I cherry-picked some upstream improvements for python3 module: > Could you please test if still an issue with uwsgi 2.0.17.1-6? I just tested and I don't get any crash during reload or shutdown. Thanks a lot for digging into this!
Bug#909653: New upstream 18 available
Source: slurm-llnl Severity: wishlist Dear maintaner, it would be nice to have the new slurm 18 version available in Debian. Thanks -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-rc4-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system)
Bug#909421: Warning from ldconfig
Package: libscotch-6.0 Version: 6.0.6-1 Severity: normal Since the latest update, I have the following warning from ldconfig: Processing triggers for libc-bin (2.27-6) ... ldconfig: /usr/lib/x86_64-linux-gnu/libesmumps-6.so is not a symbolic link -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-rc4-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libscotch-6.0 depends on: ii libbz2-1.0 1.0.6-9 ii libc62.27-6 ii liblzma5 5.2.2-1.3 ii libopenmpi3 3.1.2-4 ii zlib1g 1:1.2.11.dfsg-1 libscotch-6.0 recommends no packages. libscotch-6.0 suggests no packages.
Bug#903112: [Pkg-zfsonlinux-devel] Bug#903112: Waits for spl build directory
On Thu, Sep 20 2018, Aron Xu wrote: > It's still possible to happen when upgrading both of the packages, > pre-depends only avoids the problem on fresh installation. Let's think > about an alternative way to solve incompatible kernel problem. Do the dkms triggers actually run concurrently? I never experienced this. On the contrary, running two builds of zfs for two different kernel versions seem to break the build process. I also have 4 kernels versions installed. I'd like to avoid zfs/spl having some dkms build-exclusive rules like aufs does, since I cannot easily test the module on kernel from experimental. I'd rather have the build fail because the build truly failed. Waiting in configure looks ridiculous to me. The headers might simply not be there. The build of spl could have failed. There are not cases to wait for.
Bug#903112: Waits for spl build directory
Package: zfs-dkms Version: 0.7.9-3 Followup-For: Bug #903112 After reading through config/kernel.m4, I encourage the debian package of zfs-dkms to add: --with-spl-timeout=0 to the configure invocation. Concurrent build of spl and dkms is *not* possible in debian, as spl is listed as a pre-depends for zfs. The current behavior stalls the build process if any incompatible kernel happens to be installed. This shouldn't happen. And this happens too often: the *current* kernel happens to be incompatible. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-rc3-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.69 ii dkms 2.6.1-1 ii lsb-release9.20170808 ii spl-dkms 0.7.9-3 Versions of packages zfs-dkms recommends: ii linux-libc-dev 4.18.8-1 pn zfs-zed ii zfsutils-linux 0.7.9-3 zfs-dkms suggests no packages.
Bug#909084: [Pkg-zsh-devel] Bug#909084: Missing pcre module
On Tue, Sep 18 2018, Axel Beckert wrote: > Reason seems that pcre2 and pcre3 are not exchangable without code > changes at all as it initially sounded in that LP bug report: > > https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1792544/comments/8 > https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1792544/comments/9 > https://bugs.launchpad.net/ubuntu/+source/zsh/+bug/1792544/comments/21 It's also a very unfortunate numbering of pcre I have to say [!].
Bug#909084: Missing pcre module
Package: zsh Version: 5.6.2-2 Severity: normal In the last release, the pcre module does not seem to be built anymore. This causes "setopt rematch_pcre" to fail: failed to load module `zsh/pcre': /usr/lib/x86_64-linux-gnu/zsh/5.6.2/zsh/pcre.so: cannot open shared object file: No such file or directory -pcre-match not available for regex -- Package-specific info: Packages which depend, recommend, suggest or enhance a zsh package and hence may provide code meant to be sourced in .zshrc: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-==-== ii zshdb 0.92-3 alldebugger for Z-Shell scripts Packages which provide vendor completions: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-==-==-==-== ii curl 7.61.0-1 amd64 command line tool for transferring data wi ii git-annex 6.20180913-1 amd64 manage files with git, without checking th ii git-buildpackage 0.9.10 allSuite to help with Debian packages in Git ii khal 1:0.9.8-1 allStandards based CLI and terminal calendar ii mpv1:0.29.0-dmo1 amd64 Free and open-source general-purpose video ii ninja-build1.8.2-1amd64 small build system closest in spirit to Ma ii pass 1.7.3-1alllightweight directory-based password manag ii pulseaudio 12.2-2 amd64 PulseAudio sound server ii radare22.9.0+dfsg-1 amd64 free and advanced command line hexadecimal ii ripgrep0.9.0-6amd64 Recursively searches directories for a reg ii silversearcher-ag 2.1.0-1amd64 very fast grep-like program, alternative t ii systemd239-9 amd64 system and service manager ii systemd-container 239-9 amd64 systemd container/nspawn tools ii systemd-coredump 239-9 amd64 tools for storing and retrieving coredumps ii taskwarrior2.5.1+dfsg-6 amd64 feature-rich console based todo list manag ii udev 239-9 amd64 /dev/ and hotplug management daemon ii youtube-dl 2018.09.10-1 alldownloader of videos from YouTube and othe The following files were modified: /etc/systemd/logind.conf /etc/systemd/resolved.conf /etc/systemd/journald.conf dpkg-query: no path found matching pattern /usr/share/zsh/vendor-functions/ -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-rc3-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zsh depends on: ii libc6 2.27-6 ii libcap2 1:2.25-1.2 ii libtinfo6 6.1+20180714-1 ii zsh-common 5.6.2-2 Versions of packages zsh recommends: ii libc6 2.27-6 ii libncursesw6 6.1+20180714-1 Versions of packages zsh suggests: ii zsh-doc 5.6.2-2
Bug#907749: New upstream 1.41.0 available
Package: slic3r-prusa Version: 1.39.2+dfsg-1 Severity: wishlist Dear mantainer, Slic3r-PE has just released a new upstream version: 1.41.0.
Bug#905913: sane-backends: Don't install into testing
Package: libsane Version: 1.0.25-4.1 Followup-For: Bug #905913 The upload of 1.0.27-1~experimental6 makes libsane currently uninstallable on sid. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libsane depends on: ii acl2.2.52-3+b1 ii adduser3.117 ii libavahi-client3 0.7-4 ii libavahi-common3 0.7-4 ii libc6 2.27-5 ii libgphoto2-6 2.5.19-1 ii libgphoto2-port12 2.5.19-1 ii libieee1284-3 0.2.11-13 ii libjpeg62-turbo1:1.5.2-2+b1 ii libsane-common 1.0.25-4.1 ii libtiff5 4.0.9-6 ii libusb-1.0-0 2:1.0.22-2 ii udev 239-7 Versions of packages libsane recommends: pn libsane-extras pn sane-utils Versions of packages libsane suggests: pn avahi-daemon pn hplip
Bug#907037: Could Suggest: glslang-tools
Package: glslang-dev Version: 7.8.2853-1 Severity: wishlist I think it would make sense if glslang-dev would Suggest: glslang-tools -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system)
Bug#904952: RFP: openmvs -- open Multi-View Stereo reconstruction library
Package: wnpp Severity: wishlist * Package name: openmvs Version : 0.8 Upstream Author : OpenMVS authors * URL : https://cdcseacave.github.io/openMVS/ * License : AGPL3+ Programming Lang: C++ Description : open Multi-View Stereo reconstruction library OpenMVS aims at filling that gap by providing a complete set of algorithms to recover the full surface of the scene to be reconstructed. The input is a set of camera poses plus the sparse point-cloud and the output is a textured mesh. The main topics covered by this project are: - dense point-cloud reconstruction for obtaining a complete and accurate as possible point-cloud - mesh reconstruction for estimating a mesh surface that explains the best the input point-cloud - mesh refinement for recovering all fine details - mesh texturing for computing a sharp and accurate texture to color the mesh
Bug#904611: Crash on "Automatic reconstruction" if no GPU is supported
Package: colmap Version: 3.4-2 Severity: normal I'm using an integrated Intel UHD Graphics 620 (Kabylake GT2). I just tried "colmap gui" -> "automatic reconstruction" and left the default options (which sets GPU to enabled). colmap crashes at the following spot: #0 0x74c98f3b in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x74c9a2f1 in __GI_abort () at abort.c:79 #2 0x7508d943 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #3 0x75093896 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #4 0x750938d1 in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #5 0x557a8591 in std::thread::~thread() (this=0x56e3e498, __in_chrg=) at /usr/include/c++/7/thread:135 #6 0x557a8591 in colmap::Thread::~Thread() (this=0x56e3e490, __in_chrg=) at ./src/./util/threading.h:105 #7 0x557a8591 in colmap::internal::FeatureWriterThread::~FeatureWriterThread() (this=0x56e3e490, __in_chrg=) at ./src/./feature/extraction.h:120 #8 0x557a8591 in colmap::internal::FeatureWriterThread::~FeatureWriterThread() (this=0x56e3e490, __in_chrg=) at ./src/./feature/extraction.h:120 #9 0x556f01fb in std::default_delete::operator()(colmap::Thread*) const (this=, __ptr=) at /usr/include/c++/7/bits/unique_ptr.h:78 #10 0x556f01fb in std::unique_ptr >::~unique_ptr() (this=0x56b4c4c0, __in_chrg=) at /usr/include/c++/7/bits/unique_ptr.h:268 #11 0x556f01fb in colmap::SiftFeatureExtractor::~SiftFeatureExtractor() (this=0x56b4c040, __in_chrg=) at ./src/./feature/extraction.h:35 #12 0x556f02e9 in colmap::SiftFeatureExtractor::~SiftFeatureExtractor() (this=0x56b4c040, __in_chrg=) at ./src/./feature/extraction.h:35 #13 0x5573072b in std::default_delete::operator()(colmap::Thread*) const (this=, __ptr=) at /usr/include/c++/7/bits/unique_ptr.h:78 #14 0x5573072b in std::unique_ptr >::reset(colmap::Thread*) (__p=, this=0x56cd9fd0) at /usr/include/c++/7/bits/unique_ptr.h:376 #15 0x5573072b in colmap::AutomaticReconstructionController::RunFeatureExtraction() (this=this@entry=0x56cd9c80) at ./src/controllers/automatic_reconstruction.cc:154 #16 0x55732348 in colmap::AutomaticReconstructionController::Run() (this=0x56cd9c80) at ./src/controllers/automatic_reconstruction.cc:124 #17 0x5584b0fc in colmap::Thread::RunFunc() (this=0x56cd9c80) at ./src/util/threading.cc:162 #18 0x750bcadf in () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #19 0x76f87f2a in start_thread (arg=0x7fffd1a52700) at pthread_create.c:463 #20 0x74d5aedf in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 The same is true in "feature extraction". I'd rather see an error message instead of a crash. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages colmap depends on: ii libc6 2.27-5 ii libceres1 1.14.0-2 ii libfreeimage3 3.17.0+ds1-5+b4 ii libgcc1 1:8.1.0-12 ii libgflags2.22.2.1-1 ii libgl1 1.0.0+git20180308-3 ii libglew2.0 2.0.0-6 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii libgomp18.1.0-12 ii libgoogle-glog0v5 0.3.5-1 ii libqt5core5a5.10.1+dfsg-7 ii libqt5gui5 5.10.1+dfsg-7 ii libqt5opengl5 5.10.1+dfsg-7 ii libqt5widgets5 5.10.1+dfsg-7 ii libstdc++6 8.1.0-12 colmap recommends no packages. colmap suggests no packages.
Bug#879786: apt-secure man page needs to provide useful pointers for Release file info changes
Package: apt Version: 1.6.3 Followup-For: Bug #879786 I second that apt-secure should mention the use of "apt" and, in detail, "apt-get --allow-releaseinfo-change" as well (pointing to apt-get for more details on the various finger-graned flags) since the manpage of apt(1) doesn't include any relevant information on metadata changes. I don't ever use "apt", I mostly use "aptitude" or directly "apt-get" when needed. aptitude doesn't have support for prompting for releaseinfo changes, and apt-get does neither. The error message is somewhat puzzling, since apt-secure(8) contains mostly redundand information for those who know already something about the signing infrastructure and just want to acknowledge the change. Thanks.
Bug#903219: Acknowledgement (journald crashes)
On Sun, Jul 22 2018, Michael Biebl wrote: > Reading the upstream bug report, this seems to be an issue related to > s2idle and CLOCK_MONOTONIC. I'm thus inclined to close this bug report Agreed. > (or reassign to src:linux, depending on what you prefer). > This really should be raised at the upstream linux kernel devs though, > as it's unlikely to be fixed in the downstream linux kernel package. I already reported it upstream [1]. https://bugzilla.kernel.org/show_bug.cgi?id=200595 Would it do anything useful to reassign to src:linux? If not, don't bother.
Bug#459427: Patch seeking seconds on changelog vs. NEWS handling
On Sun, Jul 22 2018, Sean Whitton wrote: > The argument for including the recommendation is that a changelog is > not very useful in a binary package, except as a fallback when no > release notes are available. If you're going to dig into an upstream > changelog you will do so alongside a copy of the upstream source. So > distributing the upstream changelog in only the source package, and > not the binary package(s), makes most sense. This is all very reasonable and I agree with the rationale. I hope this can move forward.
Bug#903994: Backport support for GRUB_EARLY_INITRD_LINUX_CUSTOM
Package: grub-common
Version: 2.02+dfsg1-4
Severity: wishlist
The git version of grub2 and specifically the new grub-mkconfig tool
supports two new directives: GRUB_EARLY_INITRD_LINUX_{STOCK,CUSTOM} (see
commit a698240df0c43278b2d1d7259c8e7a6926c63112)
These allow grub to load extra initrd images early in a way that doesn't
require hand-modifying grub.cfg and most importantly persists across
update-grub invocations.
Bug#903478: New upstream 2.7.3 available
Package: python3-dateutil Version: 2.6.1-1 Severity: normal Dear maintainer, there's a newer upstream version of dateutil (2.7.3) which fixes some important issues for radicale 2.x It would be nice if the package would be updated. Thanks -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-dateutil depends on: ii python3 3.6.6-1 ii python3-six 1.11.0-2 ii tzdata 2018e-1 python3-dateutil recommends no packages. python3-dateutil suggests no packages.
Bug#903463: crash on startup / missing dependency
Package: cura Version: 3.3.1-1 Severity: important With a fresh installation, cura does not start: 2018-07-10 12:05:02,830 - DEBUG - [MainThread] PostProcessingPlugin.PostProcessingPlugin.loadScripts [155]: Begin loading of script: Stretch QQmlComponent: Component is not ready 2018-07-10 12:05:02,836 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [487]: file:///usr/lib/cura/plugins/PostProcessingPlugin/PostProcessingPlugin.qml:424:13: Type Cura.SettingTextField unavailable 2018-07-10 12:05:02,836 - ERROR - [MainThread] UM.Qt.QtApplication.createQmlComponent [487]: file:///usr/share/cura/resources/qml/Settings/SettingTextField.qml:5:1: module "QtQuick.Controls" version 2.0 is not installed There's a new dependency required: qml-module-qtquick-controls2 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cura depends on: ii cura-engine 1:3.3.0-2 ii fdm-materials 3.3.0-1 ii fonts-open-sans 1.11-1 ii python3 3.6.6-1 ii python3-pyqt5 5.11.2+dfsg-1 ii python3-pyqt5.qtopengl 5.11.2+dfsg-1 ii python3-savitar 3.3.0-1 ii python3-serial 3.4-3 ii python3-uranium 3.3.0-1 ii qml-module-qt-labs-folderlistmodel 5.10.1-4 ii qml-module-qt-labs-settings 5.10.1-4 ii qml-module-qtqml-models25.10.1-4 ii qml-module-qtquick-controls 5.10.1-2 ii qml-module-qtquick-dialogs 5.10.1-2 ii uranium-plugins 3.3.0-1 Versions of packages cura recommends: pn python3-zeroconf cura suggests no packages.
Bug#900658: Acknowledgement (Intel HD graphics display rotation broken with 2:1.20.0-2)
FIY, this is not only related to Intel, and has been fixed upstream: https://bugs.freedesktop.org/show_bug.cgi?id=106715 I tested manually the patch and it fixes the issue for me as well. Would it be possible to backport the fix into the current package? https://patchwork.freedesktop.org/series/44802/ Thanks
Bug#903219: Acknowledgement (journald crashes)
After further debugging I figured this seems to be related to the internal watchdog. I filed a bug report upstream: https://github.com/systemd/systemd/issues/9538
Bug#903219: journald crashes
Package: systemd Version: 239-5 Severity: important I noticed journald dumped core several times on this system. Unfortunately, I didn't notice earlier as these are obviously not logged on the journal and coredumpctl fails to report them. Nice. [ 6840.048179] systemd-coredump[7546]: MESSAGE=Process 418 (systemd-journal) of user 0 dumped core. [ 6840.048185] systemd-coredump[7546]: Coredump diverted to /var/lib/systemd/coredump/core.systemd-journal.0.e13febf27eb6481eb4b017aeba831de4.418.153099854700.lz4 [ 6840.048188] systemd-coredump[7546]: Stack trace of thread 418: [ 6840.048190] systemd-coredump[7546]: #0 0x7f1e5b58a420 n/a (libsystemd-shared-239.so) [ 6840.048193] systemd-coredump[7546]: #1 0x7f1e5b58bb42 internal_hashmap_iterate (libsystemd-shared-239.so) [ 6840.048195] systemd-coredump[7546]: #2 0x558f32563812 n/a (systemd-journald) [ 6840.048197] systemd-coredump[7546]: #3 0x7f1e5b74aa87 __libc_start_main (libc.so.6) [ 6840.048199] systemd-coredump[7546]: #4 0x558f32565a7a n/a (systemd-journald)` backtrace: [New LWP 418] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/lib/systemd/systemd-journald'. Program terminated with signal SIGABRT, Aborted. #0 storage_ptr () at ../src/basic/hashmap.c:326 #1 bucket_at () at ../src/basic/hashmap.c:374 #2 ordered_bucket_at () at ../src/basic/hashmap.c:382 #3 hashmap_iterate_in_insertion_order (i=0x7fff2163f530, h=0x558f33fc7078) at ../src/basic/hashmap.c:589 #4 hashmap_iterate_entry (h=h@entry=0x558f33fc7078, i=0x7fff2163f530) at ../src/basic/hashmap.c:703 #5 0x7f1e5b58bb42 in internal_hashmap_iterate (h=, i=, value=, key=, key=, value=) at ../src/basic/hashmap.c:711 #6 0x558f32563812 in ordered_hashmap_iterate () at ../src/basic/hashmap.h:259 #7 server_maybe_append_tags (s=0x7fff2163f5d0) at ../src/journal/journald-server.c:1891 #8 main (argc=, argv=) at ../src/journal/journald.c:98 -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii adduser 3.117 ii libacl1 2.2.52-3+b1 ii libapparmor1 2.12-4+b1 ii libaudit11:2.8.3-1+b1 ii libblkid12.32-0.1 ii libc62.27-3 ii libcap2 1:2.25-1.2 ii libcryptsetup12 2:2.0.3-5 ii libgcrypt20 1.8.3-1 ii libgnutls30 3.5.18-1 ii libgpg-error01.31-1 ii libidn11 1.33-2.2 ii libip4tc01.6.2-1 ii libkmod2 25-1 ii liblz4-1 1.8.2-1 ii liblzma5 5.2.2-1.3 ii libmount12.32-0.1 ii libpam0g 1.1.8-3.7 ii libseccomp2 2.3.3-3 ii libselinux1 2.8-1+b1 ii libsystemd0 239-5 ii mount2.32-0.1 ii procps 2:3.3.15-2 ii util-linux 2.32-0.1 Versions of packages systemd recommends: ii dbus1.12.8-3 ii libpam-systemd 239-5 Versions of packages systemd suggests: ii policykit-10.105-20 ii systemd-container 239-5 Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.130 ii udev 239-5 -- Configuration Files: /etc/systemd/journald.conf changed: [Journal] Storage=persistent MaxRetentionSec=3month MaxFileSec=1week /etc/systemd/logind.conf changed: [Login] KillUserProcesses=no
Bug#903112: Waits for spl build directory
Package: zfs-dkms Version: 0.7.9-3 Severity: normal If the spl module builds fails, the zfs configure scripts does a pointless wait loop during "configure": ... configure:14082: checking spl source directory configure:14140: result: /usr/src/spl-0.7.9 configure:14154: checking spl build directory I don't get it: why is this even necessary? There seems to be some specific logic about this in the configure script: --with-spl-timeout=SECS This is causing waits in orders of tens of minutes during package installation if the spl build fails, since dkms is triggering a rebuild multiple times. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-1-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zfs-dkms depends on: ii debconf [debconf-2.0] 1.5.67 ii dkms 2.3-3 ii lsb-release9.20170808 ii spl-dkms 0.7.9-3 Versions of packages zfs-dkms recommends: ii linux-libc-dev 4.17.3-1 pn zfs-zed ii zfsutils-linux 0.7.9-3 zfs-dkms suggests no packages.
Bug#902928: Cannot bring the grub menu up with Shift key along with GRUB_TIMEOUT_STYLE=hidden with GRUB_TIMEOUT=0
Package: grub-efi-amd64 Version: 2.02+dfsg1-4 Severity: important I was using grub-pc until recently, where I migrated to grub-efi-amd64. It's the same hardware (lenovo yoga x1). My grub configuration is unchanged, and consists of: GRUB_TIMEOUT=0 GRUB_TIMEOUT_STYLE=hidden I was used to hold shift during boot to bring the grub menu up during boot, which worked flawlessy. With grub-efi-amd64 it doesn't work anymore.
Bug#902690: Should Suggest: python-pygments-doc
Package: python3-pygments Version: 2.2.0+dfsg-1 Severity: wishlist It would be nice if pygments suggested it's own documentation (python-pygments-doc) in both the python and python3 flavours. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-trunk-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-pygments depends on: ii python3 3.6.6-1 Versions of packages python3-pygments recommends: ii python3-pkg-resources 39.2.0-1 Versions of packages python3-pygments suggests: ii ttf-bitstream-vera 1.10-8
Bug#902687: Should Suggest: dput-ng-doc
Package: dput-ng Version: 1.21 Severity: wishlist Since an additional documentation package is available, it would be nice if dput-ng would Suggest: dput-ng-doc Thanks -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-trunk-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dput-ng depends on: ii python3 3.6.6-1 ii python3-dput 1.21 dput-ng recommends no packages. Versions of packages dput-ng suggests: pn python3-twitter
Bug#902686: Should Suggest: dbus-1-doc
Package: libdbus-1-dev Version: 1.12.8-3 Severity: wishlist It would be nice if libdbus-1-dev suggested it's own documentation. Curreently, dbus-1-doc suggests libdbus-1-dev, but it should be the other way around: if you have the development headers installed you probably want the documentation as well. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-trunk-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libdbus-1-dev:amd64 depends on: ii libdbus-1-3 1.12.8-3 ii pkg-config 0.29-4+b1 libdbus-1-dev:amd64 recommends no packages. libdbus-1-dev:amd64 suggests no packages.
Bug#902669: Should Suggest: vdirsyncer-doc
Package: vdirsyncer Version: 0.16.2-4 Severity: wishlist Since vdirsyncer-doc is available, it would be nice to see it suggested in the vdirsyncer package. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-trunk-amd64 (SMP w/8 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages vdirsyncer depends on: ii python33.6.6-1 ii python3-atomicwrites 1.1.5-2 ii python3-click 6.7-5 ii python3-click-log 0.2.1-1 ii python3-click-threading0.4.4-1 ii python3-requests 2.18.4-2 ii python3-requests-toolbelt 0.8.0-1 vdirsyncer recommends no packages. Versions of packages vdirsyncer suggests: pn python3-requests-oauthlib
Bug#902368: File conflicts between jre-headless and jdk
Package: openjdk-11-jdk Version: 11~19-1 Severity: important Unpacking openjdk-11-jre-headless:amd64 (11~19-1) over (11~18-1) ... dpkg: error processing archive /var/cache/apt/archives/openjdk-11-jre-headless_11~19-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/jvm/java-11-openjdk-amd64/bin/jconsole', which is also in package openjdk-11-jdk:amd64 11~19-1 -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-trunk-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openjdk-11-jdk depends on: ii libc62.27-3 iu openjdk-11-jdk-headless 11~19-1 iu openjdk-11-jre 11~19-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages openjdk-11-jdk recommends: ii libxt-dev 1:1.1.5-1 Versions of packages openjdk-11-jdk suggests: pn openjdk-11-demo pn openjdk-11-source pn visualvm
Bug#902301: New upstream 3.8.6 available
Package: mlterm Version: 3.8.4-1+b1 Severity: wishlist Dear maintainer, there's a newer version of mlterm available: 3.8.6 (released 2018-06-12), fixing a couple of upstream bugs. It would be nice to update the package. Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-trunk-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages mlterm depends on: ii libc6 2.27-3 ii libgdk-pixbuf2.0-0 2.36.11-2 ii libglib2.0-02.56.1-2 ii libx11-62:1.6.5-1 ii mlterm-common 3.8.4-1+b1 Versions of packages mlterm recommends: ii mlterm-tools 3.8.4-1+b1 Versions of packages mlterm suggests: pn fonts-arphic-bsmi00lp pn fonts-arphic-gbsn00lp ii fonts-freefont-ttf 20120503-8 pn fonts-nanum | fonts-baekmuk pn fonts-vlgothic | fonts-japanese-gothic pn mlterm-im-m17nlib pn mlterm-im-scim pn mlterm-im-uim pn t1-cyrillic pn unifont pn xfonts-efont-unicode
Bug#901894: New upstream 0.6 available
Source: pycollada Severity: wishlist Dear maintainer, there's a newer version of pycollada available: v0.6 from November 2017. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-rc7-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system)
Bug#900658: Intel HD graphics display rotation broken with 2:1.20.0-2
Package: xserver-xorg-core Version: 2:1.20.0-2 Severity: normal After updating to 2:1.20.0-2 from 2:1.19.99.901-1, the ability to rotate the display via xrandr's --rotate stopped working. I'm using an Intel Corporation HD Graphics 520 [8086:1916] (rev 07) from a Lenovo Yoga 1st Gen, kms driver. The cursor is still displayed, but the screen is otherwise black in any orientation except for normal. The issue is present with kernels 4.15, 4.16 and 4.17 rc7 from experimental. Downgrading xserver-xorg-core to the previous version fixes the issue.
Bug#898851: New upstream available: 6.38
Package: ipset Version: 6.34-1 Severity: wishlist Dear maintainer, there's a new upstream source for the userland utilities of ipset (6.38) which fixes a parsing bug. It would be nice to update the package. Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-rc3-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ipset depends on: ii iptables 1.6.2-1 ii libc6 2.27-3 ii libipset3 6.34-1 ipset recommends no packages. ipset suggests no packages.
Bug#898003: Newer upstream 2.2.2 available
Package: gmic Version: 1.7.9+zart-4.1 Severity: wishlist Dear maintainer, the current upstream version of gmic is at 2.2.2. The current packaged release is more than one year old.
Bug#825970: pypy: Please package pypy3 as well now
Package: pypy Version: 6.0.0+dfsg-1 Followup-For: Bug #825970 pypy 6 is officially a dual 2.7/3.5 release. It would be very nice to have a pypy3 package. I have to keep a custom build, since I no longer develop on 2.7 since quite some time now. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pypy depends on: ii dpkg 1.19.0.5.0~reproducible1 ii libbz2-1.01.0.6-8.1 ii libc6 2.27-3 ii libexpat1 2.2.5-3 ii libffi6 3.2.1-8 ii libgcc1 1:8-20180425-1 ii libgdbm5 1.14.1-6 ii libncurses6 6.1+20180210-2 ii libsqlite3-0 3.23.1-1 ii libssl1.1 1.1.0h-2 ii libtinfo6 6.1+20180210-2 ii pypy-lib 6.0.0+dfsg-1 ii zlib1g1:1.2.11.dfsg-1 pypy recommends no packages. Versions of packages pypy suggests: ii pypy-doc 6.0.0+dfsg-1 pn pypy-tk
Bug#897035: Should Suggest: ncurses-doc
Package: libncurses-dev Version: 6.1+20180210-2 Severity: minor The old libncurses5-dev packages suggested the development documentation in ncurses-doc. It would be nice do the same in the new package. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-3-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libncurses-dev:amd64 depends on: ii libc6-dev [libc-dev] 2.27-3 ii libncurses6 6.1+20180210-2 ii libncursesw6 6.1+20180210-2 ii libtinfo6 6.1+20180210-2 ii ncurses-bin 6.1+20180210-2 libncurses-dev:amd64 recommends no packages. libncurses-dev:amd64 suggests no packages.
Bug#896158: Doesn't start since texlive update (undefined symbol: synctex_next_result)
Package: zathura Version: 0.3.9-1 Severity: normal The latest update of libsynctex1 broke the ABI, resulting in: zathura: symbol lookup error: zathura: undefined symbol: synctex_next_result There is already a bug filed against libsynctex1, but I believe a rebuild of zathura might be an easier solution then downgrading the whole tex package. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages zathura depends on: ii libc62.27-3 ii libcairo21.15.10-3 ii libgirara-gtk3-3 0.2.9-2 ii libglib2.0-0 2.56.1-2 ii libgtk-3-0 3.22.30-1 ii libmagic11:5.32-2 ii libpango-1.0-0 1.42.1-1 ii libsqlite3-0 3.23.1-1 ii libsynctex1 2018.20180416.47457-1 ii zathura-pdf-poppler 0.2.9-1 zathura recommends no packages. Versions of packages zathura suggests: ii chromium [www-browser] 66.0.3359.26-2 ii firefox [www-browser] 59.0.2-1 ii w3m [www-browser] 0.5.3-36 pn zathura-cb ii zathura-djvu0.2.8-1 ii zathura-ps 0.2.6-1
Bug#894819: Fails to start with recent wxWindows update
Package: slic3r-prusa Version: 1.39.1+dfsg-2 Severity: important FIY, the latest update of wxWindows packages broke the current version of slic3r and slic3r-prusa. I'm not sure where to file this (maybe wx should have put some Breaks), but maybe a simple rebuild could fix the issue. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages slic3r-prusa depends on: ii libboost-atomic1.62.0 1.62.0+dfsg-5 ii libboost-chrono1.62.0 1.62.0+dfsg-5 ii libboost-date-time1.62.0 1.62.0+dfsg-5 ii libboost-filesystem1.62.0 1.62.0+dfsg-5 ii libboost-geometry-utils-perl 0.15-2+b6 ii libboost-locale1.62.0 1.62.0+dfsg-5 ii libboost-log1.62.0 1.62.0+dfsg-5 ii libboost-regex1.62.0 1.62.0+dfsg-5 ii libboost-system1.62.0 1.62.0+dfsg-5 ii libboost-thread1.62.0 1.62.0+dfsg-5 ii libc6 2.27-3 ii libencode-locale-perl 1.05-1 ii libexpat1 2.2.5-3 ii libgcc11:8-20180402-1 ii libgl1 1.0.0+git20180308-1 ii libglew2.0 2.0.0-5 ii libglu1-mesa [libglu1] 9.0.0-2.1 ii libio-stringy-perl 2.111-2 ii libmath-convexhull-monotonechain-perl 0.1-1+b6 ii libmath-geometry-voronoi-perl 1.3-3 ii libmath-planepath-perl 126-1 ii libmoo-perl2.003004-1 ii libperl5.26 [libtime-hires-perl] 5.26.1-5 ii libstdc++6 8-20180402-1 pn libstorable-perl ii libtbb22017~U7-8 ii libwxbase3.0-0v5 3.0.4+dfsg-3 ii libwxgtk3.0-0v53.0.4+dfsg-3 ii perl 5.26.1-5 ii perl-base [perlapi-5.26.1] 5.26.1-5 Versions of packages slic3r-prusa recommends: ii libclass-xsaccessor-perl 1.19-2+b11 ii libio-all-perl0.87-1 ii libopengl-perl0.7000+dfsg-1 ii libpdf-api2-perl 2.033-1 ii libsvg-perl 2.84-1 ii libwx-glcanvas-perl 0.09-3+b5 ii libwx-perl1:0.9932-3 ii libxml-sax-expatxs-perl 1.33-2+b4 slic3r-prusa suggests no packages.
Bug#894730: Fails to start: doesn't accept DebianBanner anymore
Package: openssh-server Version: 1:7.7p1-1 Severity: normal DebianBanner does not seem to work correctly anymore. Upon upgrade to 7.7, the following is shown, sshd rejects the existing configuration file: /etc/ssh/sshd_config line 111: integer value invalid. The affected line is: DebianBanner no -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openssh-server depends on: ii adduser3.117 ii debconf [debconf-2.0] 1.5.66 ii dpkg 1.19.0.5.0~reproducible1 ii libaudit1 1:2.8.2-1 ii libc6 2.27-3 ii libcom-err21.44.1-1 ii libgssapi-krb5-2 1.16-2 ii libkrb5-3 1.16-2 ii libpam-modules 1.1.8-3.7 ii libpam-runtime 1.1.8-3.7 ii libpam0g 1.1.8-3.7 ii libselinux12.7-2+b2 ii libssl1.0.21.0.2o-1 ii libsystemd0238-4 ii libwrap0 7.6.q-27 ii lsb-base 9.20170808 ii openssh-client 1:7.7p1-1 ii openssh-sftp-server1:7.7p1-1 ii procps 2:3.3.13-1 ii ucf3.0038 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages openssh-server recommends: ii libpam-systemd 238-4 ii ncurses-term6.1-1 ii xauth 1:1.0.10-1 Versions of packages openssh-server suggests: pn molly-guard pn monkeysphere pn rssh pn ssh-askpass pn ufw
Bug#893107: Should Suggest: python-pywt-doc
Package: python3-pywt Version: 0.5.1-1.1+b2 Severity: wishlist Since developer documentation is available, it would be nice if python[3]-pywt would Suggest: python-pywt-doc Thanks -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-pywt depends on: ii libc6 2.27-2 ii python33.6.4-1 ii python3-numpy 1:1.13.3-2 python3-pywt recommends no packages. python3-pywt suggests no packages.
Bug#890845: HighContrast icon theme doesn't work with GTK3
On Thu, Mar 15 2018, Jeremy Bicha wrote: > On Thu, Mar 15, 2018 at 7:21 AM, Yuri D'Elia <wav...@thregr.org> wrote: >> I had a look at /usr/share/icons/HighContrast/index.theme and the file >> seems incomplete. The Directories= entry is truncated, and all the >> directory entries listing the various icon sizes are missing in the new >> version. > > Thank you for looking into this more closely. > > Are you able to report this issue upstream? Can you reproduce the issue? If so, I would be glad if you could report it. The common issue is that I'm *not* running gnome, I just use gtk3 programs, and /every time/ I reported issues upstream I get stuck in "try to use [random gnome3 tool]" limbo, or the report is immediately closed.
Bug#890845: HighContrast icon theme doesn't work with GTK3
On Wed, Feb 21 2018, Yuri D'Elia wrote: > On Tue, Feb 20 2018, Jeremy Bicha wrote: >> On Tue, Feb 20, 2018 at 5:46 AM, Yuri D'Elia <wav...@thregr.org> wrote: >>> On Mon, Feb 19 2018, Jeremy Bicha wrote: >>>> How are you setting the HighContrast icon theme? >>> >>> I set this using lxappearance, which basically sets >>> gtk-icon-theme-name=HighContrast in ~/.config/gtk-3.0/settings.ini >> >> Try setting the icon theme using gsettings. I suggest installing the >> GNOME Tweaks app and using that to set your theme. I updated just now to gnome-accessibility-themes 3.27.92-1. The problem persists also with the new package. I had a look at /usr/share/icons/HighContrast/index.theme and the file seems incomplete. The Directories= entry is truncated, and all the directory entries listing the various icon sizes are missing in the new version. I copied over icons/HighContrast/index.theme from 3.22.3-4 and it now works. So indeed it looks like a bug in the package/theme.
Bug#892841: Opening a file with O_CREAT fails
Package: smbnetfs Version: 0.6.1-1 Severity: important At least since 0.6.0, any attempt to use open(2) with O_CREAT on a mounted smb filesystem fails with EIO (Input/output error). The file is created, with has a size of 0. This is a call caused by "cp" traced with strace: openat(AT_FDCWD, "/home/ydelia/shared/file", O_WRONLY|O_CREAT|O_EXCL, 0644) = -1 EIO (Input/output error) This is what is outputed by smbnetfs with debugging enabled: ... unique: 8, opcode: CREATE (35), nodeid: 5, insize: 62, pid: 4235 create flags: 0x80c1 /server/test/file 0100644 umask=0022 create[139858764895120] flags: 0x80c1 /server/test/empty fgetattr[139858764895120] /server/test/file 2018-02-01 18:55:43.439 srv(4236)->smb_conn_srv_fstat: errno=22, Invalid argument 2018-02-01 18:55:45.454 srv(4237)->smb_conn_srv_fstat: errno=22, Invalid argument 2018-02-01 18:55:47.469 srv(4238)->smb_conn_srv_fstat: errno=22, Invalid argument release[139858764895120] flags: 0x80c1 unique: 8, error: -5 (Input/output error), outsize: 16 So it seems that smbnetfs creates the file correctly, then attempts an fstat and stops there. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smbnetfs depends on: ii libc6 2.27-2 ii libfuse2 2.9.7-1 ii libglib2.0-0 2.54.3-2 ii libsecret-1-0 0.18.5-6 ii libsmbclient 2:4.7.4+dfsg-1 Versions of packages smbnetfs recommends: ii fuse 2.9.7-1 smbnetfs suggests no packages.
Bug#892839: use_libsecret config option not available when service doesn't exist
Package: smbnetfs Version: 0.6.1-1 Severity: minor I wanted to supress the ServiceUnknown secret service warning I get every time I start smbnetfs. On my system I don't have gnome keyring or a "libsecret" compatible service. As such, I've put use_libsecret "false" in the config file, but the testing logic in the source is flawed. When I start smbnetfs I get this: ** Message: Remote error from secret service: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.secrets was not provided by any .service files 2018-02-01 18:49:33.498 4153->reconfigure_read_config_file: Error: (file: /home/ydelia/.smb/smbnetfs.conf) Invalid input line : use_libsecret"false" If the service does not exist, the configuration option for use_libsecret is also not accepted anymore. This shouldn't happen. If use_libsecret is set to false, the service shouldn't be probed at all. The same happens when using -o use_libsecret. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages smbnetfs depends on: ii libc6 2.27-2 ii libfuse2 2.9.7-1 ii libglib2.0-0 2.54.3-2 ii libsecret-1-0 0.18.5-6 ii libsmbclient 2:4.7.4+dfsg-1 Versions of packages smbnetfs recommends: ii fuse 2.9.7-1 smbnetfs suggests no packages.
Bug#890845: HighContrast icon theme doesn't work with GTK3
On Tue, Feb 20 2018, Jeremy Bicha wrote: > On Tue, Feb 20, 2018 at 5:46 AM, Yuri D'Elia <wav...@thregr.org> wrote: >> On Mon, Feb 19 2018, Jeremy Bicha wrote: >>> How are you setting the HighContrast icon theme? >> >> I set this using lxappearance, which basically sets >> gtk-icon-theme-name=HighContrast in ~/.config/gtk-3.0/settings.ini > > Try setting the icon theme using gsettings. I suggest installing the > GNOME Tweaks app and using that to set your theme. I never had to do that. I do have gsettings, but it has no effect. I downgraded to gnome-accessibility-themes 3.22.3-4 and I can see HighContrast working again. If I strace any GTK3 process, I can see that HighContrast is being al least read by GTK3 itself, but for some reason it's being ignored. I'm currently a bit busy so I didn't investigate why this is, but some typo in the gtk3 theme maybe?
Bug#890845: HighContrast icon theme doesn't work with GTK3
On Mon, Feb 19 2018, Jeremy Bicha wrote: > Ok, I looked closer and this doesn't appear to be a Tweaks bug. And I > can't reproduce the issue at all. > > On Mon, Feb 19, 2018 at 4:01 PM, Yuri D'Elia <wav...@thregr.org> wrote: >> Since the last update, the "HighContrast" icon theme only works for GTK2 >> programs. >> GTK3 programs seem stuck with the default (tango?) theme. > > Which GTK3 program? Any. "gxmessage test" shows another icon on the ok button, for example. (probably from the adwaita icon theme? I'm actually not sure). I only ever used the HighContrast theme. > How are you setting the HighContrast icon theme? I set this using lxappearance, which basically sets gtk-icon-theme-name=HighContrast in ~/.config/gtk-3.0/settings.ini > What desktop are you using? I'm not using any DE. I noticed the change because the File Open Dialog of FF (for example, it's currently using GTK3) has now the tango/ icons instead of the HighContrast I usually use. But Inkscape, which is still GTK2, still retains the HighContrast icon.
Bug#890845: HighContrast icon theme doesn't work with GTK3
Package: gnome-accessibility-themes Version: 3.27.90.1-1 Severity: normal Since the last update, the "HighContrast" icon theme only works for GTK2 programs. GTK3 programs seem stuck with the default (tango?) theme. My GTK3 config hasn't changed (.config/gtk-3.0/settings.ini has gtk-icon-theme-name=HighContrast set). -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system)
Bug#890777: Should Suggest: libglfw3-doc
Package: libglfw3-dev Version: 3.2.1-1 Severity: wishlist Since documentation is available, it would be nice if libglfw3-dev itself would Suggest: libglfw3-doc. Thanks! -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libglfw3-dev:amd64 depends on: ii libgl1-mesa-dev [libgl-dev] 18.0.0~rc4-1 ii libglfw3 3.2.1-1 Versions of packages libglfw3-dev:amd64 recommends: ii libegl1-mesa-dev 18.0.0~rc4-1 ii libvulkan-dev 1.0.65.2+dfsg1-1 ii libwayland-dev1.14.0-1+b1 ii libx11-dev2:1.6.4-3 ii libxrandr-dev 2:1.5.1-1 libglfw3-dev:amd64 suggests no packages.
Bug#890234: Error reported by doc-base
Package: nasm Version: 2.13.02-0.1 Severity: minor During doc-base setup: Setting up doc-base (0.10.8) ... Unregistering 234 doc-base files, re-registering 236 doc-base files... Error in `/usr/share/doc-base/nasm-manual', line 14: all `Format' sections are invalid. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-rt-amd64 (SMP w/4 CPU cores; PREEMPT) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nasm depends on: ii dpkg 1.19.0.5.0~reproducible1 ii install-info 6.5.0.dfsg.1-2 ii libc6 2.26-6 nasm recommends no packages. nasm suggests no packages.
Bug#888441: Newer stable version available
Package: cura Version: 3.0.3-2 Severity: wishlist Cura 3.1 is the latest available stable release. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cura depends on: ii cura-engine 1:3.0.3-2 ii fonts-open-sans 1.11-1 ii python3 3.6.4-1 ii python3-pyqt5 5.9.2+dfsg-1 ii python3-pyqt5.qtopengl5.9.2+dfsg-1 ii python3-savitar 3.0.3-3 ii python3-serial3.4-1 ii python3-uranium 3.0.3-1 ii qml-module-qt-labs-folde 5.9.2-3 ii qml-module-qt-labs-setti 5.9.2-3 ii qml-module-qtqml-models2 5.9.2-3 ii qml-module-qtquick-contr 5.9.2-2 ii qml-module-qtquick-dialo 5.9.2-2 ii uranium-plugins 1:3.2.0~201801231746~rev2120~pkg182~ubuntu18.04.1 Versions of packages cura recommends: ii fdm-materials 3.0.3-3 pn python3-zeroconf cura suggests no packages.
Bug#887847: Extra quoting needed for the job description
Package: systemd-cron Version: 1.5.12-2 Severity: normal Found this in the wild: zfsutils-linux package has the following cron.d entry: # Scrub the second Sunday of every month. 24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-linux/scrub generating this timer unit: [Unit] Description=[Timer] "24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-linux/scrub" which yields: /run/systemd/generator/cron-zfsutils-linux-root-0.timer:2: Failed to resolve unit specifiers on [Timer] "24 0 8-14 * * root [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ] && /usr/lib/zfs-linux/scrub", ignoring: Invalid slot The % should be escaped in Description as well using %%. -- Package-specific info: -- output of systemd-delta -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-cron depends on: ii libc6 2.26-4 ii python3 3.6.4-1 ii systemd-sysv 236-3 Versions of packages systemd-cron recommends: ii exim4-daemon-light [mail-transport-agent] 4.90-3 systemd-cron suggests no packages.
Bug#883087: consolation: very slow restart
On Sat, Dec 30 2017, Bill Allombert wrote: > I have uploaded consolation_0.0.6~pre1 with the --no-daemon option. > Could you write a patch to fix debian/init.d ? > I could do it but then I am not in a good position to test the result. Sorry for the delay. Attaching: consolation.path: diff for init.d/consolation to make use of --no-daemon and correct pid file (provided by start-stop-daemon). Tested and works correctly now. consolation.service: the same for systemd, using --no-daemon and Type=simple (no guesswork). Also tested. --- consolation.Orig 2018-01-20 16:09:04.708448392 +0100 +++ consolation 2018-01-20 16:15:18.366830577 +0100 @@ -47,9 +47,8 @@ # 2 if daemon could not be started start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --test > /dev/null \ || return 1 - start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON -- \ - $DAEMON_OPTS \ - || return 2 + start-stop-daemon --start --quiet --pidfile $PIDFILE --make-pidfile --background \ + --exec $DAEMON -- --no-daemon $DAEMON_OPTS || return 2 } # consolation.service Description: Binary data
Bug#883087: consolation: very slow restart
On Fri, Dec 29 2017, Bill Allombert wrote: >> It would be nice to have a non-forking mode though. > > So you would like a command line option that prevent forking ? > What should be the name ? --no-daemon ? I've seen and like "-f" for "foreground" personally, but --no-daemon is just as good: your call. This would avoid the need for a pid file in both cases: With start-stop-daemon you can combine -m -b to make a pid file for you. With systemd just change Type=simple (or remove it as it's default).
Bug#883087: consolation: very slow restart
Package: consolation Version: 0.0.5-1 Followup-For: Bug #883087 I noticed my system took too long to shutdown and tracked it down to consolation (which is awesome btw!). As mentioned by Jakub, consolation forks without writing a pid file, so start-stop-daemon just timeouts. I wrote a simple service file (attached) which sort-of solves the problem with GuessMainPID. Under systemd, the service now stops instantly. It would be nice to have a non-forking mode though. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages consolation depends on: ii libc6 2.25-5 ii libevdev2 1.5.7+dfsg-1 ii libinput10 1.9.4-2 ii libudev1236-1 ii lsb-base9.20170808 consolation recommends no packages. consolation suggests no packages. [Unit] Description=linux console pointer interface [Service] ExecStart=/usr/sbin/consolation Type=forking [Install] WantedBy=multi-user.target
Bug#885079: Should Suggest: libevdev-doc
Package: libevdev-dev Version: 1.5.7+dfsg-1 Severity: wishlist Since developer documentation is available, it would be nice if libevdev-dev would Suggest: libevdev-doc Thanks -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-1-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libevdev-dev depends on: ii libevdev2 1.5.7+dfsg-1 libevdev-dev recommends no packages. libevdev-dev suggests no packages.
Bug#872560: Related issues
FYI, this also has implications for systemd. See the following bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878965 and the related upstream: https://github.com/systemd/systemd/issues/7054
Bug#882042: ess: nil ess-etc-directory causing error upon Emacs startup
Package: ess Version: 17.11-1 Followup-For: Bug #882042 Looks like ess doesn't play well with emacsen-common. ess-lisp-directory is initialized to /usr/share/emacs25/site-lisp/ess/ in ess-utils.el:46. The ess-etc-directory-list expects to find the etc directory somewhere relative to this path, which is not true for debian. You need to explicitly eval (setq ess-etc-directory "/usr/share/ess/etc/" ess-etc-directory-list nil) before the package is loaded, or patch the default definition. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-trunk-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ess depends on: ii dpkg1.19.0.4.0~reproducible1 ii emacsen-common 2.0.8 ii install-info6.5.0.dfsg.1-1 Versions of packages ess recommends: ii r-base-core 3.4.2-2.0~reproducible1 Versions of packages ess suggests: pn jags pn julia pn pspp pn xlispstat -- debsums errors found: debsums: changed file /usr/share/emacs/site-lisp/ess/ess-utils.el (from ess package)
Bug#882226: UNW_VERSION_MINOR contains a float
Package: libunwind-dev Version: 1.2.1-2 Severity: important This is from libunwind-common.h: #define UNW_VERSION_MAJOR 1 #define UNW_VERSION_MINOR 2.1 #define UNW_VERSION_EXTRA Notice how .1 was not spilled to UNW_VERSION_EXTRA. This breaks the UNW_VERSION_CODE macro, which expects integers only. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-trunk-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libunwind-dev depends on: ii libunwind8 1.2.1-2 libunwind-dev recommends no packages. libunwind-dev suggests no packages.
Bug#882127: Cannot be installed in unstable due to libc6 update
Package: apitrace Version: 7.1+git20170623.d38a69d6+repack-2 Severity: normal Dear maintainer, apitrace-tracers has an explicit version restriction on libc6<2.25, which now cannot be satisfied on unstable. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc7-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apitrace depends on: ii apitrace-tracers 7.1+git20170623.d38a69d6+repack-2 ii libbsd0 0.8.6-3 ii libc6 2.24-17 ii libgcc1 1:7.2.0-18+really14.0~reproducible1 ii libpng16-16 1.6.34-1 ii libprocps62:3.3.12-3 ii libsnappy1v5 1.1.7-1 ii libstdc++67.2.0-18+really14.0~reproducible1 ii libwaffle-1-0 1.5.2-4 ii libx11-6 2:1.6.4-3 ii python2.7.14-1 ii python-imaging4.3.0-2 ii zlib1g1:1.2.8.dfsg-5 apitrace recommends no packages. apitrace suggests no packages.
Bug#881250: Should only Recommend: javascript-common
Package: libjs-jed Severity: normal libjs-jed shouldn't depend on javascript-common directly, unless a web server is actually required (which isn't). The dependency should be changed to a recommends. Thanks. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc7-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libjs-jed depends on: pn javascript-common libjs-jed recommends no packages. libjs-jed suggests no packages.
Bug#880126: Should Recommend: python3-sqlalchemy-ext
Package: python3-sqlalchemy Version: 1.1.11+ds1-1 Severity: normal python3-sqlalchemy should Recommend: python3-sqlalchemy-ext, as python-sqlalchemy is already doing. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc5-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-sqlalchemy depends on: ii python3 3.6.3-2 python3-sqlalchemy recommends no packages. Versions of packages python3-sqlalchemy suggests: ii python-sqlalchemy-doc 1.1.11+ds1-1 pn python3-fdb pn python3-mysqldb ii python3-psycopg2 2.7.3-1
Bug#880125: Should Recommend: python3-openpyxl, python3-xlrd
Package: python3-pandas Version: 0.20.3-10 Severity: normal Loading of various Excel documents depends on python3-openpyxl and python3-xlrd. Both were already Recommended in python-pandas, but the same is not true for python3-pandas. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc5-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-pandas depends on: ii python33.6.3-2 ii python3-dateutil 2.6.1-1 ii python3-numpy 1:1.13.1-1 ii python3-pandas-lib 0.20.3-10 ii python3-pkg-resources 36.2.7-2 ii python3-six1.11.0-1 ii python3-tz 2017.2-2 Versions of packages python3-pandas recommends: pn python3-bs4 ii python3-html5lib0.9-1 ii python3-lxml4.0.0-1 ii python3-matplotlib 2.0.0+dfsg1-2+b1 ii python3-numexpr 2.6.2-2 ii python3-scipy 0.19.1-1 ii python3-tables 3.4.2-1 Versions of packages python3-pandas suggests: ii python-pandas-doc 0.20.3-10
Bug#879000: Cannot recover after password timeout
Package: dracut Version: 045+132-1 Severity: normal I briefly tried dracut on a minimal system with cryptosetup+luks root filesystem. Everything works as expected. I discovered a minor issue with the password prompt. During boot, the prompt to unlock the root fs has a timeout. If the timeout is reached, you're dropped onto a recovery shell. At this stage, unfortunately, the password prompt seems to be still active and is still eating half of the keypresses in the background, making it impossible to actually use the recovery shell. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-rc3-amd64 (SMP w/4 CPU cores) 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 /bin/dash Init: systemd (via /run/systemd/system) Versions of packages dracut depends on: ii dracut-core 045+132-1 dracut recommends no packages. Versions of packages dracut suggests: pn dracut-network
