I confirm that this issue has been fixed (along with bug 1062932). It
should be marked as done.
On Tue, 13 Feb 2024 07:13:55 +0200 Teemu Likonen wrote:
> This is probably the same bug as #1062932
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062932
Indeed!
The reason why I filed this bug against linux-image-6.1.0-18-amd64 is
that it was installing it that triggered the problem.
Nicholas D Steeves wrote:
> To all affected users: Do you remember if you ever manually installed
> an affected elpa-package from sid/unstable or from testing? I'm
> curious if this might be part of the trigger condition.
Before the upgrade to bookworm I was running an almost pure bullseye.
The
After upgrading to bookworm I also got bitten by this issue. Otherwise
the upgrade went smoothly.
I noted that at least for some of the superfluous files, the cruft tool
(from package cruft-ng) reports that a file belongs to the package
emacs, while it does not according to dpkg -L or dpkg -S:
Johannes Schauer Marin Rodrigues wrote:
> Yes. This is because if you just run "mmdebstrap --unshare-helper
> /usr/sbin/chroot" then it will do nothing else then do a chroot into
> the given directory. Since you cannot create any device nodes as the
> unshared user, /dev/null is missing. You can
Johannes Schauer Marin Rodrigues wrote:
> $ mmdebstrap --include=hello testing - | tar -C /tmp/fakechroot -x
This is perfect for my purposes, thanks!
signature.asc
Description: PGP signature
Johannes Schauer Marin Rodrigues wrote:
> Thank you, your input was very valuable because proot was essentially
> broken since 16 August 2021 and I was waiting for somebody to tell me
> that they are a proot user and why they need it. You are a proot user
> but it seems that creating the chroot
Package: mmdebstrap
Version: 0.7.5-2.2
Severity: normal
Dear Maintainer,
Running mmdebstrap in proot mode seems no longer to work,
For example the command
mmdebstrap --mode=proot unstable ./unstable-chroot
fails with the following output:
I: chroot architecture amd64 is equal to the host's
My main usage of geeqie is quickly browsing through many photos,
selecting the ones that I want to keep. This involves using marks and
repetitively switching back and forth between images, and has become
unbearably slow with this bug.
For now I worked around the problem by downgrading to geeqie
It seems to me that this is primarily not an upstream issue but
a problem of the Debian package itself.
The pylint upstream Python package does not install any non-standard
Emacs key bindings. It only provides en elisp file with code (function
'pylint-add-key-bindings') that will do so if called
Yangfl wrote:
> Not a bug but an opinion or a question. See
> https://bugs.launchpad.net/ubuntu/+source/oomd/+bug/1898155 , discuss
> with the upstream or come up with your config proposal.
Thanks for the pointer. I did not know that the default config that is
shipped by Debian is provided by
Package: oomd
Version: 0.4.0-1+b1
Severity: normal
Dear Maintainer,
It’s great that bullseye proposes a solution to the dreaded problem of system
freeze under memory pressure.
However, at least on my machine, oomd intervenes too late with the default
configuration which is supposed to be
Package: wnpp
Severity: wishlist
Owner: Christoph Groth
* Package name: qsymm
Version : 1.2.7
Upstream Author : Qsymm authors
* URL : https://gitlab.kwant-project.org/qt/qsymm
* License : BSD
Programming Lang: Python
Description : Symmetry finder
Enrico Zini wrote:
> This happens with me because the interface appears in the screen where
> the mouse is: try moving the mouse cursor towards the screen that is
> on, and the login window should come with it.
For me this was not the case. The UI would appear for half a second
immediately
On Sun, 5 Jan 2020 19:19:39 +0100 Alf wrote:
> Now I discovered this posting from Dai_trying:
> (...)
>
> And that really works without any glitches for over a week so far.
> (...)
I tried Alf’s workaround on a laptop on which Debian buster with an Xfce
desktop was installed recently. I use
I filed this bug only after verifying during one night that it does not
occur with xscreensaver. However, now I just observed it after a
suspend period of a couple of hours. The package xfce4-screensaver
cannot be the culprit, since it is no longer installed.
Package: xfce4-screensaver
Version: 0.1.8-1
Severity: important
Dear Maintainer,
I upgraded to Xfce 4.14 from Debian bullseye. This involved xfce4-screensaver
from unstable. (I'm actually unsure why it got installed. I have unstable in
the APT-sources, but APT::Default-Release is set to
Package: mmdebstrap
Version: 0.4.1-3
Severity: normal
Thanks a lot for mmdebstrap, it's extremely useful!
I noticed a minor problem with it. According to the manpage, if proot is
installed, mmdebstrap should chooose proot-mode by default. I do not observe
this behavior. When I explicitly give
Unison 2.51.2 that has been released in January 2018 has a new feature
that is very useful for synchronizing, for example, '.git' directories:
> Add a new preference, 'atomic', for specifying directories that should
> be treated atomically.
It would be great to see this in Debian soon!
Here is the (closed) corresponding upstream issue that explains why
upstream intents to keep the current behavior:
https://github.com/pypa/virtualenv/issues/1279
I can confirm the existence of this problem and that it renders baobab
almost unusable (there are, however, workarounds).
Normally, when the mouse cursor hoovers over a sector of the ring chart
of baobab, that sector becomes highlighted and black labels with the
names of the sub-directories
My mbsync (isync package) setup stopped working for a particular IMAP
server because of this bug. I get the following error message:
Socket error: secure connect to imap.server.com (1.2.3.4:993):
error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small
(In the above message,
Thanks Dingyuan, uninstalling djvulibre-desktop solved the problem for
me. Should this bug be transferred to djvulibre-desktop then?
Package: python3-args
Version: 0.1.0-2
Severity: important
Dear Maintainer,
The 'args' module that is provided by this package is unusable when any
command line argument is present in Python's 'sys.args':
$ python3 -c 'import args' foo
Traceback (most recent call last):
File "", line 1, in
ITP for tinyarray:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886628
Package: wnpp
Severity: wishlist
Owner: Christoph Groth <christ...@grothesque.org>
* Package name: tinyarray
Version : 1.2.0
Upstream Author : Christoph Groth <christoph.gr...@cea.fr>
* URL : https://gitlab.kwant-project.org/kwant/tinyarray
* License
Package: wnpp
Severity: wishlist
Owner: Christoph Groth <christ...@grothesque.org>
* Package name: kwant
Version : 1.3.2
Upstream Author : Kwant authors <auth...@kwant-project.org>
* URL : http://www.kwant-project.org/
* License : BSD
Programming
As demonstated above the problem is reproducible.
Please excuse the cruft at the begin of the report. I used
reportbug's --body-file option to send a saved report and it added
the template. Seems like a bug in reportbug!
of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Christoph Groth <christ...@grothesque.org>
To: Debian Bug Trac
was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Christoph Groth <christ...@grothesque.org>
To: Deb
Unison’s "-repeat watch" feature is very useful, I second the
request to package it for Debian.
Is there some technical problem blocking this, or is it just lack
of time?
Package: python-scipy-doc
Version: 0.18.1-2
Severity: minor
Dear Maintainer,
It seems that python-scipy-doc, just like python-numpy-doc, should be
registered with Debian's doc-base, so that the documentation can be easily
found.
-- System Information:
Debian Release: stretch/sid
APT prefers
Since gnupg2 is the default now (As of version 2.1.11-7+exp1 of
the gnupg package), it seems that this bug can be closed now.
Package: network-manager-gnome
Version: 1.0.6-2
Severity: normal
Dear Maintainer,
When running nm-connection-editor (that can be also launched by
right-clicking on the nm-applet icon and choosing "Edit Connections"),
I am unable to edit or delete existing connections (the buttons are
grayed
Here is the missing URL of the bug [1]:
https://github.com/numpy/numpydoc/issues/5
Package: python-numpydoc
Version: 0.4-1
Severity: normal
Dear Maintainer,
The package python-numpydoc 0.4 has at least one annoying bug [1] that leads
to spurious warnings when Sphinx documentation is being built. This problem
has been fixed in version 0.5. Please consider packaging 0.5 for
While I noticed this bug with linux-image-4.0.0-2-amd64 version
4.0.8-1,
it seems to have disappered with 4.0.8-2.
signature.asc
Description: PGP signature
Dererk wrote:
This is due to repacking applied at source tarball for
DFSG-compliance,
since some minifications (mainly distributed as .min.*) are
currently
considered non-dfsg-compliant on the Debian project.
Please see debian/README.source.
But surely making a package DFSG compliant
The archive nikola_7.6.0.orig.tar.xz as present in Debian lacks
many files that are present in nikola-7.6.0.tar.gz as found on
https://pypi.python.org/simple/nikola/. How can this be?
$ diff -r nikola-7.6.0-debian nikola-7.6.0-pypi
Only in
Hi!
I also suffer from this bug, it appeared at least a few months
ago. I noticed it in connection with bug 762257. I'm willing to
help with this issue, but unfortunately I do not have any
experience with the geeqie code base.
I use geeqie to preview and select the RAW files that I shoot
Unfortunately, the problem still persists. It did not appear in a
directory of portrait-format photos that I was browsing, but this
is just an exception. The problem seems to be triggered for large
images of some minimum size (width?).
Sorry for the confusion.
--
To UNSUBSCRIBE, email to
I confirm the observation of Alex Goebel, i.e. that this problem
was independent of image and zoom settings.
I noticed another issue that might have been related: When
browsing through directories of images, the value showed in the
last column of the output of the command free (i.e. cached)
Indeed, the problem is independent of the image/zoom settings. It
must be related to fullscreen mode, as it seems never to occur
before geeqie is sent into fullscreen mode. But once geeqie has
been fullscreen at least once, it is somehow tainted and 1:1
becomes slow both in normal and
Package: geeqie
Version: 1:1.2-1
Severity: normal
Dear Maintainer,
Since a recent upgrade, image refresh at 1:1 zoom became very slow. This
problem is linked to the option Two pass rendering in Preferences/Image.
Unchecking it makes the problem disappear.
I can reproduce the issue as
This bug has been fixed upstream in version 2.11:
http://cgit.freedesktop.org/xkeyboard-config/commit/?id=098880078deb91b737bcfdfbdcd82eef73202792
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: sslh
Version: 1.13b-3.2
Severity: normal
Dear Maintainer,
sslh's README.Debian states
sslh needs a webserver that has ssl support (for example mod_ssl for Apache)
If not, sslh seems to be useless.
However, sslh works perfectly without a webserver as well. For example, It can
be used
Package: aptitude
Version: 0.6.8.2-1
Severity: normal
Dear Maintainers,
I noticed that specifying different sorting orders with aptitude search does
lead to differing numbers of results being reported. For example
$ aptitude search ~i^lib | wc -l
1027
$ aptitude -O name search ~i^lib | wc -l
Package: python-matplotlib-dbg
Version: 1.1.1~rc2-1
Severity: important
Dear Maintainer,
Importing matplotlib.pyplot fails for the -dbg version of matplotlib:
$ python-dbg -c 'import matplotlib.pyplot'
Traceback (most recent call last):
File string, line 1, in module
File
From: christoph.gr...@cea.fr
Subject: altwin:ctrl_alt_win does not map Win to Ctrl keys
To: Sergey V. Udaltsov s...@gnome.org
Date: Fri, 15 Mar 2013 09:50:27 +0100 (1 day, 23 hours, 44 minutes ago)
The following patch for the file /usr/share/X11/xkb/symbols/altwin
seems to solve the problem
Nothing special here:
% locale
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
Package: mnemosyne
Version: 2.0~RC1-2
Severity: normal
When choosing the menu entry Settings - Configure Mnemosyne, a window with the
following error message appears
Uncaught exception!
Traceback (innermost last):
File /usr/lib/python2.7/dist-packages/mnemosyne/pyqt_ui/main_wdgt.py, line
192,
Package: aptitude
Version: 0.6.8-1
Severity: normal
Very recently, the following problem occurred on my box which is running Debian
testing:
aptitude full-upgrade wanted to install texlive-fonts-extra (and many MBs of
packages that texlive-fonts-extra depends upon), though this was not
Source: openoffice.org-dictionaries
Severity: normal
Dear Maintainer,
the Debian package dictionaries-common makes installed dictionaries
automatically known to programs like emacs, jed and mutt. This is
described under http://dict-common.alioth.debian.org/.
The dictionary packages made from
No, the extension runs when installed from within the browser. This is
version 2.1.10.
Do you know how I could debug (i.e. get more information than There was
an error starting Zotero.) this issue?
Thus the bug you report is upstream and has nothing to do with the package
(which is btw
I installed xul-ext-zotero. When I try to launch it from within
iceweasel I get the message There was an error starting Zotero.
Unfortunately I don't have an amd64 machine to test for this. I
suggest trying to install the extension from upstream to see if
there's the same problem.
No, the
Package: xul-ext-zotero
Version: 2.1.8-2
Severity: important
Dear Maintainer,
I installed xul-ext-zotero. When I try to launch it from within iceweasel I
get the message There was an error starting Zotero.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy:
Package: xserver-xorg-video-nouveau
Version: 1:0.0.16+git20101210+8bb8231-2
Severity: important
This problem occurred today after upgrading to the most recent state of
Debian testing.
The package xserver-xorg-video-nouveau was upgraded, but as it does not
depend on a linux 2.6.38, the installed
Cyril, thank you for your quick reply.
Cyril Brulebois k...@debian.org writes:
The package xserver-xorg-video-nouveau was upgraded, but as it does
not depend on a linux 2.6.38, the installed kernel was still version
2.6.32. Subsequently, the xserver failed to start (logfile included
below).
Package: pylint
Version: 0.21.1-1
Severity: normal
Tags: upstream
pylint.el defines the following key bindings
C-c m l pylint
C-c m n next-error
C-c m p previous-error
According to
http://www.gnu.org/software/emacs/elisp/html_node/Key-Binding-Conventions.html
such
Hello,
I'm also affected by this bug which is quite annoying. My machine is a
Dell Latitude D430 (945GME chipset) running Debian testing. For me, the
problem manifests itself not only in the way Florian described but also
in perforated fonts in some applications as described in this posting
Colin Watson [EMAIL PROTECTED] writes:
Please attach /etc/ssh/sshd_config, and look for relevant entries around
sshd startup time in /var/log/auth.log.
After running /etc/init.d/ssh restart only two lines are appended to
/var/log/auth.log:
Sep 2 08:08:28 mimoid sshd[3807]: Received signal
Package: openssh-server
Version: 1:5.1p1-2
Severity: important
After openssh-server was upgraded from 1:4.7p1-12 to 1:5.1p1-2 all connection
attempts (from local and remote systems) fail, e.g.:
mimoid:~# ssh localhost
ssh: connect to host localhost port 22: Connection refused
mimoid:~# telnet
Package: grub
Version: 0.97-13
Severity: critical
Justification: breaks the whole system
Yesterday I upgraded my etch-system with
aptitude dist-upgrade
grub was upgraded from version 0.97-12 to version 0.97-13. During the
upgrade the file /boot/grub/menu.lst was updated incorrectly, the
64 matches
Mail list logo
