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
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?
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
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
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
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]:
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
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
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,
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
>>
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?
&
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
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
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
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,
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
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'),
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'),
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,
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
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
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
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
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
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.
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')
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
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
Package: screenkey
Severity: minor
python-xlib is not required by screenkey.
You must depend on libx11-6 explicitly.
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
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,
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')
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
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:
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,
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)
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
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
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
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)
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
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?
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
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
>
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
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
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
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.
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,
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
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.
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
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
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
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
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 :(
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:
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.
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 o
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
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
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?
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
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.
On Tue, Feb 04 2020, Nicholas D Steeves wrote:
>> This makes libqt5core5a uninstallable for me. I have several programs
>> which still depend on libqtcore4. I also still develop on qt4.
>
> FYI https://lists.debian.org/debian-devel-announce/2017/08/msg6.html
> and
Package: libxcb-xinput-dev
Version: 1.13.1-4
Severity: important
The new version cannot be installed as it depends on
"libxcb-xfixes0-dev." (typo with a trailing dot).
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
Package: libpango-1.0-0
Version: 1.44.7-3
Followup-For: Bug #939748
I was wondering why "dunst", suddenly, stopped displaying characters,
even though dunst itself didn't change.
Looking at the upgrade log, I catch pango, and now I see this.
I generally don't use bitmap fonts, but they have their
Package: opencascade
Version: 7.3.3+dfsg1-2
Severity: minor
My understanding is that when choosing to include the version in the
package name of a library, is that so that we can allow for multiple
versions of the library to coexist on the same system.
However all libocct-* 7.4 libs break 7.3,
Package: systemd
Version: 245.5-1
Severity: minor
A time-keeping daemon is not always needed (guest OSes being the primary
example).
I know systemd-timesyncd was built-in up to 245.4-1, but it would be
nice to drop the hard dependency nonetheless so that I can avoid masking
the service entirely.
Package: maim
Version: 5.5.3-1
Severity: important
I didn't realize maim depended on slop through a dso (I assumed it
simply called the binary).
slop was updated to 7.5, which broke maim as a result:
maim: error while loading shared libraries: libslopy.so.7.4: cannot open shared
object file:
Package: aptitude
Version: 0.8.12-3
Followup-For: Bug #498241
I encountered this problem today. I'm trying to match all packages which
will upgraded on the next run, but turns out to be non-trivial.
'~U' includes packages with holds and forbids (and according to the
description: "packages that
Package: debdelta
Version: 0.65
Severity: minor
There's a new deprecation warning that popped up recently:
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
-- System
Package: libyaml-cpp0.6
Version: 0.6.3-4
Followup-For: Bug #959201
This ABI breakage also affects blender (indirecly via opencolorio).
Version 0.6.3-4 does fix the symbol lookup error, however blender will
incur a crash soon after with a segmentation fault.
Downgrading libyaml-cpp0.6 to 0.6.2-4
Package: libboost-dev
Version: 1.71.0.3
Severity: wishlist
It would be nice to have a package for an updated version of boost.
I've ran into a couple of packages that expect features from 1.73
already.
At the time of writing, upstream is at 1.74
Package: wine-development
Version: 5.5-5
Severity: wishlist
The current development package is a bit lagging against upstream.
Upstream's wine-development is at 5.18.
Package: meshio-tools
Version: 4.0.16-1
Severity: normal
Caught during install:
Setting up meshio-tools (4.0.16-1) ...
Traceback (most recent call last):
File "/usr/bin/pypy3compile", line 186, in
main()
File "/usr/bin/pypy3compile", line 178, in main
py_compile.compile(module,
Package: elpa-magit
Version: 2.99.0.git0957.ge8c7bd03-1
Severity: important
The newer git version removes the dependency on elpa-magit-popup which
seems to be required:
...
In toplevel form:
magit-tag.el:30:1:Error: Cannot open load file: No such file or directory,
magit-popup
In toplevel
On Tue, Jul 07 2020, Rémi Vanicat wrote:
> Could you show me the line 30 of the file
>
> /usr/share/emacs/site-lisp/elpa-src/magit-2.99.0/magit-tag.el
(require 'magit)
> Also please check if there is another version of magit installed in
> /root/.emacs.d or in /usr/local/share/emacs/site-lisp/
Package: hunspell-en-us
Version: 1:2019.10.06-1
Severity: minor
For an embarassingly long time I was wondering why
aspell/ispell/hunspell wouldn't handle correctly anything basic with
apostrophes, such as "isn't".
Turns out I read the explaination, by random chance, here:
Package: screenkey
Severity: wishlist
A new upstream version of screenkey (1.1) is officially available, which
should fix bug #962118 as well.
Additionally, the package dependencies are incomplete.
screenkey should also depend explicitly on required GI interface
gir1.2-gtk-3.0.
I would also
Package: sauerbraten
Version: 0.0.20140302-2
Severity: wishlist
Dear maintainer, there seems to be a newer version of sauerbraten
available: the "2020 edition".
It would be nice to have an update!
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900,
Package: src:linux
Version: 5.10.4-1
Severity: normal
Starting with 5.10, kernel dies when attempting to connect to a 802.1x
network, showing the following trace:
[ 232.661980] Oops: [#5] SMP NOPTI
[ 232.661987] CPU: 5 PID: 2131 Comm: iwd Tainted: G DOE
5.10.0-1-amd64 #1
Package: libjs-popper.js
Version: 1.16.1+ds-2
Severity: minor
libjs-popper.js 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 or less.
Thanks.
On Thu, Jan 07 2021, Salvatore Bonaccorso wrote:
> Is this potentially the same as
> https://lore.kernel.org/keyrings/67250277-7903-2005-b94b-193bce0a3...@markus-regensburg.de/
> ?
Excellent catch, same scenario (and even hardware it seems)!
I created a new report earlier today:
Package: freecad
Version: 0.19~pre1+git20201123.8d73c8f0+dfsg1-1
Severity: important
freecad is searching modules in /usr/lib/freecad/Mod, however
freecad-common has them in /usr/share/freecad. Startup fails with:
Log: Init: starting App::FreeCADInit.py
Wrn: No modules found in
On Sat, Nov 21 2020, Sven Joachim wrote:
>> If the mlterm package changed that ut-default setting, then providing your
>> own termcap settings may have reset the behavior to match the compiled-in
>> NON-ut default.
>
> That seems to have hit the mark. Indeed, if ":ut" is added to Yuri's
> termcap
Package: ncurses-term
Version: 6.2+20201114-1
Severity: normal
With the latest version, it seems that the
mlterm/mlterm3/mlterm-256color definitions are somewhat broken. The
background color set by term programs (say, aptitude) is not set
correctly anymore.
Switching to
On Fri, Nov 20 2020, Sven Joachim wrote:
> Which version of mlterm do you use?
I'm also using mlterm 3.9.0-1.
So after some scrambling, I have a custom ~/.mlterm/termcap config to
override the sequence sent by F[1-4]:
mlterm-256color:\
k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~
Removing
On Sat, Nov 21 2020, Sven Joachim wrote:
>>> mlterm-256color:\
>>> k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~
>>>
>>> Removing this (so that mlterm sends it's usual \EOP/*) fixes the
>>> background-color rendering.
>>>
>>> I'm puzzled as of why this override would influence this at all?
>>
>>
It seems that the current version is 13.00, released March 2020,
at the new URL: https://dn-works.com/ufas/
Package: bluez
Version: 5.55-3
Followup-For: Bug #986005
Upstream is now at 5.58
Source: linux
Version: 5.10.28-1
Followup-For: Bug #986995
I can confirm any device controlled by the acm driver has issues
starting with 5.10.28. Sometimes it's possible to just replug the serial
device to fix the issue, however for devices that reconnect after reset,
there's no work-around.
On Sun, Apr 25 2021, Yuri D'Elia wrote:
> Relevant upstream bug reports:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=212751
> https://bugzilla.kernel.org/show_bug.cgi?id=212725
FIY the proposed/accepted patch:
https://lore.kernel.org/linux-usb/20210421074513.4327-1-oneu...@
Package: rlwrap
Version: 0.43-1+b2
Severity: wishlist
Dear maintainer, upstream has released 0.45. It would be nice to update
due to several bug fixes affecting the current package.
Thanks!
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900,
Package: bluez
Version: 5.55-3
Severity: wishlist
Dear maintainer, there seems to be a newer version of bluez 5.56
available.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture:
Package: openjdk-17-jre-headless
Version: 17~14-1
Severity: normal
Just tried to run "josm" on openjdk-17, but I get the following error:
021-03-21 19:27:07.757 SEVERE: Handled by bug report queue:
java.lang.UnsatisfiedLinkError:
/usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so:
Package: src:linux
Version: 5.10.13-1
Severity: wishlist
Recently our department upgraded some wireless Cisco equipment and as a result
I'm no longer able to connect to the wifi network.
The relevant part from the kernel shown during association is:
RX AssocResp from 4c:a6:4d:54:09:4c
Package: libell-dev
Version: 0.36-1
Severity: wishlist
Upstream released ell 0.39
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP
Package: pulseeffects
Severity: wishlist
Hi maintainers,
Since pipewire is now available in unstable, would it be possible to
support for using pulseeffects directly with a pipewire daemon?
Would the current package/build already work with pipewire, or would
pulseeffects require a different
601 - 700 of 765 matches
Mail list logo
