Small addendum, in case it helps tracking down the issue: quite curiously,
clicking below a tab character on the last line of the buffer still works
correctly, it selects the tab itself.
Source: vim
Version: 2:9.0.1378-2
Severity: normal
X-Debbugs-Cc: matthijsvand...@gmail.com
Dear Maintainer,
Clicking anywhere in a tab character other than its leftmost column
causes the cursor to be placed on the next character after the tab
instead of putting it on the tab character itself.
Package: vim-runtime
Version: 2:9.0.1378-1
Severity: normal
X-Debbugs-Cc: matthijsvand...@gmail.com
Dear Maintainer,
I noticed when editing perl code in vim that pressing enter after the
opening brace of a subroutine no longer indents like you'd expect:
// expected:
sub foo {
Package: systemd
Version: 250.4-1
Severity: normal
Tags: patch upstream
X-Debbugs-Cc: matthijsvand...@gmail.com
Dear Maintainer,
Since systemd v250 (bookworm/testing), the LLDP packets transmitted by
systemd-networkd (with EmitLLDP=on) are malformed, causing debian systems
running bookworm to be
FS_READY property in an initramfs script but
for some reason it doesn't seem to get set, even though udev should be
running if I understand correctly. I didn't get around to try using
"btrfs device ready" since I found a much easier workaround:
apt-get install dracut
apt-get purge initramfs-tools-core
Matthijs van Duin
Package: libsystemd0
Version: 241-7~deb10u2
Severity: normal
When an sd-event io event source with fd ownership is released while it
is dispatching (i.e. from inside the event callback), the event source
is freed after dispatching is complete but it fails to close the fd.
This bug has recently
I got the message "Unable to revert mtime: /usr/local/share/fonts"
(see also related bug 909728) upon opening a particular pdf file with
xpdf and discovered this message was emitted after it had created a
.uuid file in that directory (which was writable by me as normal user,
probably something I
On Tue, 5 Feb 2019 at 19:53, Antoine Beaupré wrote:
> I guess I could just drop the "python" dependency from there completely
> and rely on the bzr bits to do the right thing if they are setup.
Yes, in principle you could write out git | (bzr, python) as git |
bzr, git | python but this feels
Package: etckeeper
Version: 1.18.10-1
Severity: normal
Dear Maintainer,
"apt-get install etckeeper" on one of my systems advised me:
The following additional packages will be installed:
libpython-stdlib libpython2-stdlib libpython2.7-minimal
libpython2.7-stdlib python
On 10 August 2018 at 18:50, Simon McVittie wrote:
> Which nss-mdns version are you using?
0.14.1-1
> What's in the hosts: line in your /etc/nsswitch.conf?
I currently have:
hosts: files mymachines mdns_minimal resolve [!UNAVAIL=return] dns
myhostname
but I also tried some
The following patch fixes the problem for me:
diff --git c/src/util.c w/src/util.c
index aaebd62..594ed42 100644
--- c/src/util.c
+++ w/src/util.c
@@ -62,7 +62,7 @@ int verify_name_allowed_with_soa(const char* name, FILE*
mdns_allow_file) {
case VERIFY_NAME_RESULT_ALLOWED:
return
This problem seems to be cause by the local_soa() call in src/util.c that I
presume was introduced as part of this "feature" listed in NEWS:
* nss-mdns now implements [standard
heuristics](https://support.apple.com/en-us/HT201275) for
detecting `.local` unicast resolution and will
Package: systemd
Version: 238-4
Severity: normal
Tags: upstream
Dear Maintainer,
sd_bus_open_system_remote() is currently broken in testing/unstable, and
as a result so are systemctl and busctl with --host argument. This is a
regression introduced in v238.
A fix is available upstream:
I've found the problem, it has nothing to do with cross-gcc. The issue lies
with the native gcc 6.2 which has been configured with
--enable-default-pie, which (at least on arm) breaks its ability to link
any code produced by earlier compilers.
Package: gcc-6-arm-linux-gnueabihf
Version: 6.1.1-9cross1
Severity: important
Dear Maintainer,
If I cross-compile any code (even a basic hello-world) and then attempt
to link the resulting objects on the target system (stretch, armhf)
using the native gcc-6 toolchain (which is 6.2.0 in testing
Package: binutils-arm-linux-gnueabihf
Version: 2.25.1-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After upgrading binutils-arm-linux-gnueabihf to 2.25.1-2 it fails to
link anything whatsoever. Even a trivial program, e.g.
echo 'int main() { return 0; }' |
On 8 August 2015 at 01:18, Axel Beckert a...@debian.org wrote:
Matthijs: I'd close this bug with 0.7-1+b1 if you confirm.
The crashes are gone indeed.
The... cosmetic... issue I mailed you about is still present. Should I
file a new bug report on that? I'm still not quite sure how to phase
On 7 August 2015 at 09:22, Axel Beckert a...@debian.org wrote:
This one is probably in aptitude itself. So they're probably different
issue. Keeping them in one bug report for the moment, though, until
someone can pinpoint the cause more precise than me.
It appears to be memory corruption, so
I just noticed aptitude and libcwidget3v5 still depend on
libsigc++-2.0-0c2a, shouldn't that be libsigc++-2.0-0v5 now?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: aptitude
Version: 0.7-1
Severity: important
Dear Maintainer,
Since upgrade to 0.7, aptitude's TUI has become unusable for me due to
consistent crashes, in particular occuring:
1. if I set the package tree limit, in either view
2. if I perform a search
2. if I open the menu bar (^T) and
The option seems to have been renamed to altwin_swap_alt_win
Original xpdf 3.03 works fine, the problem is that debian's xpdf links
against libpoppler while retaining much duplicate code. In particular,
both xpdf and libpoppler have a GlobalParams class and a globalParams
global variable, and the two get confused at runtime: libpoppler's
GlobalParams
I've hit this bug too in a fresh squeeze install with the SLiM display
manager. It seems the problem is that stdin remains opened to
/dev/console when slim invokes Xsession and indirectly dbus-launch,
which then monitors stdin in a way that apparently causes keystrokes
to be lost on the console.
23 matches
Mail list logo
