Bug#1040638: Bothersome message every day from cron

(Klaus, did you really mean to close this bug report with your last message? I'll go ahead and reopen it since I'm also affected by this bug.) >From what I understand, this bug affects entries of the form `/dev/md0` in `mdadm.conf`, and was introduced by commit 84d969be, which now always looks

Bug#1034661: twinkle: Please update twinkle to latest release

On Fri, Apr 21, 2023 at 04:46:20PM +1000, Jason Lewis wrote: > Please can you update twinkle to the latest release version 1.10.3 > > this will at least solve https://github.com/LubosD/twinkle/issues/222 (Upstream co-maintainer speaking.) To provide some context: the domain name once used by

Bug#1015722: nvme-cli: Broken Bash completion due to syntax errors

On Tue, Jul 19, 2022 at 04:12:52PM -0400, Frédéric Brière wrote: > /usr/share/bash-completion/completions/nvme contains two syntax errors, > resulting in tab completion actually aborting the current command line. I stand slightly corrected: this exact behavior is not caused by these syntax

Bug#1015722: nvme-cli: Broken Bash completion due to syntax errors

Package: nvme-cli Version: 1.16-4 Severity: normal Tags: patch /usr/share/bash-completion/completions/nvme contains two syntax errors, resulting in tab completion actually aborting the current command line. See attached patch for a fix. -- System Information: Debian Release: bookworm/sid APT

Bug#1006189: /usr/bin/xdg-mime: `xdg-mime query default` blindly greps through .desktop files

Package: xdg-utils Version: 1.1.3-4.1 Severity: normal File: /usr/bin/xdg-mime Demonstrating under XFCE (though I think it affects all but KDE): $ cat /usr/local/share/applications/foobar.desktop [Desktop Entry] # blah blah blah text/unreadable; blah x-scheme-handler/foo; blah blah blah

Bug#1005770: ucommon: new upstream release 7.0.1

Source: ucommon Version: 7.0.0-19 Severity: wishlist Although the main page still lists 7.0.0 as the latest version, 7.0.1 has been tagged and tarballed on Savannah[1] for some time. This version most notably compiles with GCC 11, thus fixing #984373. [1]

Bug#990911: liferea: Segfaults when selecting a news bin

Package: liferea Version: 1.13.5-1 Severity: important Tags: upstream, fixed-upstream, patch liferea 1.13.5 will immediately segfault when selecting a news bin in the left pane. (And if a news bin was the last selected item before upgrading, it will then automatically crash on startup. I'd

Bug#983880: xpdf: Printing fails, apparently due to broken PostScript output

Package: xpdf Version: 3.04+git20210103-1 Severity: normal Attempting to print any (non-trivial) PDF document with xpdf 3.04+git20210103-1 results in a "No pages found!" CUPS error. Downgrading to 3.04-14 fixes the issue. This seems to be caused by a broken PostScript output; printing to a file

Bug#974597: kiten: Segfaults on startup if KConfigGui::sessionConfig() returns nullptr

Package: kiten Version: 4:20.04.3-1 Severity: important Tags: patch kiten invariably segfaults on startup for me: #0 0x7f3833a898ff in KConfigBase::hasGroup (this=0x0, group=group@entry=0x561e19ce44a3 "app") at ./src/core/kconfigbase.cpp:22 #1 0x561e19cd660a in Kiten::finishInit

Bug#965903: xjdic: Removal of obsolete debhelper compat 5 and 6 in bookworm

Control: tags -1 + patch Reviewing the list of changes between debhelper compat levels 5 and 13, the only one affecting xjdic is the removal of "dh_clean -k". After switching to dh_prep, the build works fine under compat level 13, and the resulting package is identical according to diffoscope.

Bug#957985: xjdic: ftbfs with GCC-10

Control: tags -1 + patch Given how xjdic is unmaintained upstream, it's probably better to simply re-enable -fcommon, rather than trying to fix the source itself. (Similary to iftop's #957357, of which I shamelessly copied the commit summary line.) >From 6b4b299de3aaa6773fbb32868e0b282ac5cd4c49

Bug#960083: libsane1: 99-libsane1.rules should not invoke setfacl for USB interfaces

Package: libsane1 Version: 1.0.28-1~experimental2 Severity: normal Plugging in my USB scanner results in the following error being logged three times: systemd-udevd[1277237]: 5-1:1.1: Process '/bin/setfacl -m g:scanner:rw ' failed with exit code 2. This is due to the fact that a udev 'add'

Bug#939536: qemu-system-data: qemu.desktop is missing Exec entry

On Fri, Sep 06, 2019 at 12:10:21AM -0400, Shmerl wrote: > The desktop entry file "/usr/share/applications/qemu.desktop" has Type= > "Application" but no Exec line > > I tried to submit the bug upstream, but I can't access launchpad bug tracker > used by Qemu, their log-in system is broken (at

Bug#950890: xserver-xorg-core: X segfaults when displaying a big image with xzgv

On Mon, Feb 10, 2020 at 10:30:44AM +0100, Michel Dänzer wrote: > Can't see the backtrace, It was attached as gdb.txt. (Granted, I could've renamed it to something a bit more obvious.) > but the log excerpt above looks like the fixes > from

Bug#950890: xserver-xorg-core: X segfaults when displaying a big image with xzgv

Package: xserver-xorg-core Version: 2:1.20.7-2 Severity: important I can (reliably) get X to segfault when displaying a big image (say, over 1x1) with xzgv. And since that viewer allows doubling the scale of an image with a single keystroke, this can easily be triggered with any image

Bug#947145: libucommon-dev: #include unexpectedly defines NDEBUG

Package: libucommon-dev Version: 7.0.0-16 Severity: normal When included, ucommon/ucommon.h (via platform.h) unexpectedly defines NDEBUG without any warning, unless DEBUG has already been defined. That led to a lot of head-scratching, trying to figure out why assert() was sometimes, but not

Bug#917185: udev 240-1 + sysvinit-core 2.93-1 break input devices + other problems

On Sun, Dec 23, 2018 at 10:11:08AM -0300, Ricardo F. Peliquero wrote: > After updating udev from 239-15 to 240-1 I found these problems: I just filed #917247 (about some modules no longer loaded at boot), and some of your problems might be related to this: > * Wireless keyboard + mouse don't

Bug#915197: sane-utils: saned is always started regardless of setting in /etc/default/saned

Package: sane-utils Version: 1.0.27-1 Severity: normal # dpkg-reconfigure --frontend readline sane-utils Configuring sane-utils -- [...] Enable saned as a standalone server? [yes/no] no [...] [] Restarting SANE network scanner server: saned[] Stopping

Bug#885756: choqok: Interface is missing many icons

On Wed, Apr 11, 2018 at 12:34:54PM -0400, Frédéric Brière wrote: > Quick followup: I've seen the same thing happen with another KDE > application (KAddressBook), so this is most likely not specific to > Choqok after all. I take that back: this is quite possibly a Choqok bug

Bug#885756: choqok: Interface is missing many icons

Quick followup: I've seen the same thing happen with another KDE application (KAddressBook), so this is most likely not specific to Choqok after all. (At this point, I would usually reassign the bug report myself, but I have no clue on which of the various KDE packages it should belong to.)

Bug#891541: lua-posix: Loading fails with "module 'posix.ctype' not found"

Package: lua-posix Version: 33.4.0-2 Severity: important (Filing as important instead of grave, since I don't know if it affects everyone.) After upgrading from 31-3 to 33.4.0-2: $ lua Lua 5.2.4 Copyright (C) 1994-2015 Lua.org, PUC-Rio > require 'posix'

Bug#890093: twinkle: Does not need to build-depend on qtscript5-dev

Source: twinkle Severity: normal Twinkle has never actually used QtScript, as far as I can tell. Rather, it uses embedded JavaScript in QML, which is all part of qtdeclarative. (This build-dep was also removed upstream in a42de5e.) For the record, build-depending on qttools5-dev-tools is also

Bug#885756: choqok: Interface is missing many icons

On Fri, Dec 29, 2017 at 01:40:50PM -0500, Frédéric Brière wrote: > If I can figure out where the current icons are coming from, maybe I'll > be able to find where the other icons are supposed to be. Basically, the icons that work are those provided by the choqok package itself (under /usr

Bug#885756: choqok: Interface is missing many icons

On Fri, Dec 29, 2017 at 03:36:01PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Hi! Maybe your are not running KDE? It might be missing some dependency. Good point; I am indeed running XFCE instead. If I can figure out where the current icons are coming from, maybe I'll be able to find

Bug#885756: choqok: Interface is missing many icons

Package: choqok Version: 1.6-2 Severity: normal After upgrading from 1.5-5+b2 to 1.6-2, the new interface seems to be missing many (most?) icons, resulting in empty buttons. See the attachments for a few examples. (Notice how in the lower left corner of a tweet, only the ReSend icon is

Bug#876928: qbittorrent: Please have qbittorrent-dbgsym file instead of qbittorrent-dbg

On Tue, Sep 26, 2017 at 11:12:10PM +, shirish शिरीष wrote: > It would be nice if you could move from qbittorrent-dbg to > qbittorrent-dbgsym. From my limited experience of debugging, the > experience has been dbgsyms give much more info. AFAIK, there should be no difference between the two

Bug#875908: qbittorrent fails to start with "symbol lookup error"

On Fri, Sep 15, 2017 at 10:11:35PM +0200, Carlo Marchiori wrote: > symbol lookup error: /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5: undefined > symbol: FT_Get_Font_Format > > libfreetype.so.6 => /usr/local/lib/libfreetype.so.6 (0x7f078671c000) What happens if you move your locally-compiled

Bug#869921: apt: Pinning the local version of a package no longer works

Package: apt Version: 1.1 Severity: normal Pinning the local version of a package, as documented in apt_preferences(5), seems to have been broken between jessie and stretch: Contents of /etc/apt/preferences: Package: hello Pin: origin "" Pin-Priority: 999 Output of "apt-cache

Bug#860560: qbittorrent process not terminated after closing program

On Tue, Apr 18, 2017 at 06:33:38PM +0200, Beatrice Torracca wrote: > whenever I close qbittorrent (Menu File -> Exit), the program seems > closed but it really is not. > > Apparently the code S means it is sleeping, but it stays like that > forever (or I never saw it go away) unless I kill it. >

Bug#859047: pysolfc: Any stack of Hanafuda cards is always movable

Package: pysolfc Version: 2.0-4 Severity: normal Tags: patch Any stack of Hanafuda cards is always deemed movable, even if it is out of sequence. The effect can easily be seen a game such as Firecracker, where: - Any stack can be dragged as a whole (but not released) - "Highlight piles" will

Bug#853801: qjoypad: segfaults on left click

tags 853801 + patch thanks On Tue, Jan 31, 2017 at 08:19:18PM -0500, Frédéric Brière wrote: > Left-clicking on the systray icon (or on the main window with --notray) > immediately triggers a segfault: > > #1 0x5616b57ba023 in QString::~QString() (this=0x7ffd91e48d50, > __in

Bug#853797: xjdic: May crash on long definitions when looking up plain form verbs

tags 853797 + patch thanks >From be96ccf4dc68f3f0a4d6573bb24fbea29f65d11a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fr=C3=A9d=C3=A9ric=20Bri=C3=A8re?= Date: Thu, 16 Mar 2017 15:45:36 -0400 Subject: [PATCH] Make vline[] big enough to hold the largest definition in edict ---

Bug#857971: xjdic: Eventually segfaults after EOF

Package: xjdic Version: 24-10 Severity: normal Tags: patch $ xjdic < /dev/null > /dev/null Segmentation fault xjdic never checks the result of getchar() against EOF, resulting in an infinite loop, which eventually segfaults. The simplest solution is to check and exit in getcharxx(), before

Bug#857968: xjdic: Does not display spaces in definitions past 80 columns

Package: xjdic Version: 24-10 Severity: normal Tags: patch On a display wider than 80 columns, spaces will be omitted from long definitions past column 80. -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable')

Bug#857594: /usr/bin/edict-grep: should invoke grep with --text

Package: edict Version: 2016.12.06-1 Severity: normal File: /usr/bin/edict-grep edict-grep sounds like a nice idea. Thanks Leonardo! $ edict-grep something Binary file /usr/share/edict/edict matches Well, that was certainly less than helpful. :) Adding --text to $grepopts solves this

Bug#856029: qbittorrent: Getting qbittorrent 3.3.10 in debian

FYI, qbittorrent 3.3.8+ will not build with the version of libtorrent-rasterbar currently in Debian (1.1.1), so any upgrade past 3.3.7 is blocked until 1.1.2 (released upstream two weeks ago) is packaged. Your best option at the moment is probably to file a wishlist bug for libtorrent-rasterbar,

Bug#820460: reprepro: Omitting Release from DebIndices still generates that file

reopen 820460 notfixed 820460 5.1.0-1 thanks I'm still getting the same behavior with 5.1.1-1: $ grep DebIndices conf/distributions DebIndices: Packages . .gz .xz DebIndices: Packages . .gz .xz DebIndices: Packages . .gz .xz DebIndices: Packages . .gz .xz $ find -name '*Release*'

Bug#855073: qbittorrent: Data Loss after reboot

On Tue, Feb 14, 2017 at 09:01:01AM +0500, Khurram Mahmood wrote: > *HiIn my case I think the force recheck didnt do any good. (Sorry for the delay.) A recheck alone will not suffice; qBittorrent is no longer looking in the right location, so it assumes all files are now missing. > *Kindly

Bug#855658: xautolock: Cannot locate a running xautolock after -restart

Package: xautolock Version: 1:2.2-5.1 Severity: normal After xautolock has been restarted once, any attempt to talk to it will fail: $ xautolock -restart $ xautolock -restart Could not locate a running xautolock. This is a bit problematic, since "xautolock -restart" is invoked by

Bug#855553: git-pbuilder: Add a quiet/silent option to disable "set -x"

Package: git-buildpackage Version: 0.8.12.2 Severity: wishlist git-pbuilder unconditionally issues a "set -x" before invoking the builder; since this outputs to stderr, this makes it rather difficult to perform a silent run (such as in a cron job) without discarding any error message. -- System

Bug#842538: libtorrent-rasterbar9: Upgrading from 1.1.0-3 to 1.1.1-1 breaks qbittorrent

On Fri, Nov 25, 2016 at 12:10:57PM +0100, bruno zanetti wrote: > It looks like the two versions are ABI incompatible and a soname bump was > required. For the record, upstream solved this issue by reverting to the old behavior, which is actually compatible with both ABIs. > OTOH, qbittorrent

Bug#855073: qbittorrent: Data Loss after reboot

On Tue, Feb 14, 2017 at 01:57:20AM +0500, Khurram Mahmood wrote: > On system rebooting, it has occurred 3rd time, that an already downloaded > torrent restarted from zero percent. Yes, I've had a similar experience in the past with 3.3.6-1. From what I understand, this is due to a bug[1] in

Bug#853798: mpv: Segfaults on TV input

On Mon, Feb 06, 2017 at 10:25:41PM +, James Cowgill wrote: > Does it work when applied on top of 0.23? Sorry for the delay. Yes, aaad2d8 applies cleanly on top of v0.23.0, and fixes the bug there as well.

Bug#843819: gnome-terminal: Parenthesis in the directory name leads to crash

On Sat, Feb 04, 2017 at 02:07:17PM -0600, Jason Crain wrote: > This looks like a problem in bash. I've recently come across this bug myself. There seem to be two elements necessary to trigger it, at least in my case: - A long current directory pathname, including at least one non-ASCII

Bug#853798: mpv: Segfaults on TV input

found 853798 0.21.0-1 tag 853798 + upstream forwarded 853798 https://github.com/mpv-player/mpv/issues/4096 thanks Thanks for your quick (and detailed) reply! On Wed, Feb 01, 2017 at 11:29:38AM +, James Cowgill wrote: > Unfortunately I can't reproduce this issue (I don't have any TV input >

Bug#853801: qjoypad: segfaults on left click

Package: qjoypad Version: 4.1.0-2 Severity: important Left-clicking on the systray icon (or on the main window with --notray) immediately triggers a segfault: #0 0x5616b57ba023 in QBasicAtomicInt::deref() (this=0x7ffd) at /usr/include/qt4/QtCore/qatomic_x86_64.h:133 #1

Bug#853798: mpv: Segfaults on TV input

Package: mpv Version: 0.23.0-1 Severity: important mpv quickly segfaults (before displaying any video) on TV input: $ mpv tv:// Playing: tv:// [tv] Selected driver: v4l2 [tv] name: Video 4 Linux 2 input [tv] Selected device: BT878 video (Hauppauge (bt878)) [tv] Tuner cap: [tv]

Bug#853797: xjdic: May crash on long definitions when looking up plain form verbs

Package: xjdic Version: 24-10 Severity: normal xjdic may trigger a buffer overflow on long definitions when looking up plain form verbs, which occurs when fed an inflected verb in kanji form: $ echo '出て' | xjdic [...] *** buffer overflow detected ***: xjdic terminated [...] Aborted

Bug#852755: libkf5i18n-dev: should depend on gettext

Package: libkf5i18n-dev Version: 5.28.0-1 Severity: normal KF5I18NMacros.cmake invokes find_package(Gettext REQUIRED). -- System Information: Debian Release: 9.0 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign

Bug#852750: libreadline7: readline() interferes with blocked SIGALRM

Package: libreadline7 Version: 7.0-1 Severity: normal Tags: patch upstream Forwarded: https://lists.gnu.org/archive/html/bug-readline/2017-01/msg2.html Control: affects -1 twinkle-console readline() in 7.0-1 calls pselect() with an empty sigmask, thereby unblocking all signals beforehand.

Bug#846779: xserver-xorg-core: chrome freezes with xorg-server 1.19.0

On Tue, Dec 13, 2016 at 05:08:15PM +0900, Michel Dänzer wrote: > Did you not run into that while bisecting? > > [...] > > Actually, that one wasn't a complete freeze, DRI2 clients would limp on > as long as one would e.g. move the mouse. :) That may explain why you > didn't notice it when

Bug#846779: xserver-xorg-core: chrome freezes with xorg-server 1.19.0

On Wed, Jan 11, 2017 at 04:50:02PM +0100, Andreas Boll wrote: > [1] https://patchwork.freedesktop.org/patch/132089/ Yup, this seems to do the trick. I only tested it briefly, but I could no longer immediately trigger the bug after applying this patch. (And reverting it makes mpv freeze again

Bug#849586: reportbug incorrectly short-circuits From address escaping with non-ASCII characters

On Wed, Dec 28, 2016 at 02:53:17PM -0800, Russ Allbery wrote: > According to a thread on debian-devel, reportbug generated a From header > looking like: > > From: =?utf-8?b?VG9tYXMgTWFydGnFoWl1cyA8dG9tYXNAcHVnYS52ZHUubHQ+?= I was also bitten by this bug this morning. Thank you for the bug

Bug#850058: libass5: mpv often segfaults when displaying status info

Package: libass5 Version: 0.13.5-1 Severity: important After upgrading libass5 to 0.13.5-1, mpv routinely segfaults when issueing commands that display some status information. For example, it always segfaults immediately on P (display progress bar) or PgUp/Down (next/previous chapter), and is

Bug#846779: xserver-xorg-core: chrome freezes with xorg-server 1.19.0

On Sat, Dec 10, 2016 at 10:07:51PM -0500, Frédéric Brière wrote: > Otherwise, I guess I'll have to muster up the courage to try to bisect > this. (gulp!) It wasn't exactly a nice leisurely stroll through the park, but I did manage to bisect and pinpoint f993091 as the guilty

Bug#846779: xserver-xorg-core: chrome freezes with xorg-server 1.19.0

On Sat, Dec 10, 2016 at 10:07:51PM -0500, Frédéric Brière wrote: > - Furthermore, I can't seem to reproduce this bug under a different >user. Maybe something to do with a different WM/compositor >configuration? I take that back; I've finally managed to reproduce this

Bug#846779: xserver-xorg-core: chrome freezes with xorg-server 1.19.0

On Sun, Dec 11, 2016 at 09:08:25AM +, Gerrit Keller wrote: > Indeed I can confirm this happening with mpv. Though here it takes only a > few seconds to freeze. I've since realized that I could improve the odds by launching several instances in parallel; at least one of them is bound to freeze

Bug#846779: xserver-xorg-core: chrome freezes with xorg-server 1.19.0

On Sat, Dec 03, 2016 at 11:33:30AM +0100, Gerrit Keller wrote: > after upgrading to version 1.19.0-(1,2) chromium/google-chrome freezes after a > short time. I'm experiencing the same thing with mpv; it eventually freezes after a while (between 1 and 20 minutes, no obvious pattern) under

Bug#844350: coreutils: unable to chroot in wheezy directory made with git-pbuilder

On Sat, Dec 10, 2016 at 08:42:29PM -0500, Frédéric Brière wrote: > If I'm not mistaken, this is basically a duplicate of #844350. That should have been #845942.

Bug#844350: coreutils: unable to chroot in wheezy directory made with git-pbuilder

On Mon, Nov 14, 2016 at 05:43:00PM +0100, Andrea Zagli wrote: > i try to use git-pbuilder to build a package for wheezy; but after run the > command 'DIST=wheezy git-pbuilder create' i got a segmentation fault when it > tries to chroot If I'm not mistaken, this is basically a duplicate of

Bug#799843: googleearth-package: generated package depends on lsb-core which is not available on sid

On Mon, Oct 17, 2016 at 12:24:16PM +0200, Graham Inggs wrote: > Please confirm if this was fixed by the upload of lsb 9.20161016. lsb-compat does indeed do the trick. Thanks!

Bug#830523: I was apparently wrong...

On Sun, Jul 17, 2016 at 01:11:25PM +0300, Shai Berger wrote: > Further, there is no need for two X servers to be running -- one is enough, > provided that it is made not active. I confirm. Thanks!

Bug#830523: xserver-xorg-input-libinput: segfaults upon plugging back a USB keyboard when two X servers are running

Package: xserver-xorg-input-libinput Version: 0.19.0-1 Severity: normal I normally have two X servers running, and have recently encountered this bug: after unplugging and plugging back my USB keyboard (or, more likely, turning off/on my monitor which acts as a USB hub), the latter action will

Bug#823971: mutt: Ignores /etc/mailcap and ~/.mailcap files

On Tue, May 10, 2016 at 02:45:44PM -0600, Bob Proulx wrote: > The recent version 1.6.0-1 ignores both ~/.mailcap and /etc/mailcap > files. At least for text/html entries. Same here. As far as I can tell, only text/html entries are affected. This seems to have been triggered by the removal of

Bug#820460: reprepro: Omitting Release from DebIndices still generates that file

package reprepro tags 820460 -moreinfo +patch thanks On Sun, Apr 10, 2016 at 12:11:16PM +0200, Bernhard R. Link wrote: > * Frédéric Brière <fbri...@fbriere.net> [160408 18:51]: > > Release files are still generated, despite having > > "DebIndices: Packages . .g

Bug#820468: mutt: tag-replying to encrypted messages does not encrypt by default

Package: mutt Version: 1.5.24-1+b1 Severity: normal When tag-replying to encrypted messages, Mutt does not select any encryption by default (unlike when replying to a single message). This somewhat unexepected behavior could result in sensitive information being sent in the clear, if one is not

Bug#820465: mutt: Replying to encrypted message in cleartext will sign instead if pgp_autoinline=yes

Package: mutt Version: 1.5.24-1+b1 Severity: normal This is a weird one. The steps to reproduce: 1. :set pgp_autoinline=yes 2. Reply to an encrypted message 3. Change Security from "Encrypt (inline PGP)" to "None" 4. Send Mutt will then proceed as if "Sign (inline PGP)" had been

Bug#820462: reprepro: Please add an --ignore option for --export=never warnings

Package: reprepro Version: 4.17.0-1 Severity: wishlist Specifying --export=never will trigger a "no index file was exported" warning, which can result in a slew of messages when performing a batch of multiple operations (which is the typical case for --export=never). An --ignore option to silence

Bug#820460: reprepro: Omitting Release from DebIndices still generates that file

Package: reprepro Version: 4.17.0-1 Severity: normal The documentation for DebIndices states that omitting the optional Release filename will result in no file being generated. This does not appear to work for me; Release files are still generated, despite having "DebIndices: Packages . .gz .xz"

Bug#230695: xjdic: Doesn't work with UTF-8

On Wed, Aug 08, 2007 at 01:57:34PM -0400, Frédéric Brière wrote: > I was thinking of giving this issue a try when a little Googling turned > up a very thorough patch from Phillip Vandry that makes xjdic > locale-aware: <http://tzone.org/~vandry/xjdic/xjdic-24.locale.patch>. There's

Bug#810551: python-pil: ambiguous package name 'python-pil' in maintainer scripts

Package: python-pil Version: 3.0.0-1 Severity: important Attempting to configure or remove python-pil will fail if more than one instance of this package is present: dpkg-query: error: --listfiles needs a valid package name but 'python-pil' is not: ambiguous package name 'python-pil' with

Bug#792552: still not working for me

On Fri, Jan 08, 2016 at 08:49:44AM +0100, Harald Dunkel wrote: > metoo. My /etc/crypttab contains just a comment line. Indeed, the applied patch will loop infinitely when given an empty crypttab. Conversely, it will fail to loop if a busy entry is followed by a non-busy one. Here's a quick fix

Bug#801157: notification-daemon:amd64: Notification body is blank when containing a

Package: notification-daemon Version: 3.18.0-1 Severity: normal If the body of a notification contains a tag, notification-daemon will display an empty body for that notification. $ notify-send 'Summary' 'Body line 1Body line 2' -- System Information: Debian Release: stretch/sid APT

Bug#791169: libsidplayfp: library transition may be needed when GCC 5 is the default

On Mon, Aug 17, 2015 at 08:29:38PM +0200, László Böszörményi wrote: May I ask you what patch do you mean Merely the one from message #10, renaming the package after a rebuild; not a code patch per se. you experience? I've uploaded a new upstream release for the GCC 5 transition and that

Bug#791169: libsidplayfp: library transition may be needed when GCC 5 is the default

Thank you Julien (and Steve) for the patch; now audacious no longer segfaults on startup. Much appreciated.

Bug#786844: xjdic: Multiple buffer overflows

Package: xjdic Version: 24-9 Severity: normal Tags: upstream patch [ Although buffer overflows are often regarded as security bugs, I'm filing this bug with normal severity, on the advice of the security team. ] There are several possible buffer overflows throughout the xjdic code (at least in

Bug#783778: automysqlbackup: Add support for xz compression

Package: automysqlbackup Severity: wishlist Tags: patch Here's a patch adding support for xz compression to the current gzip/bzip2 alternatives. A similar patch was submitted, and subsequently rejected by upstream, several years ago[1]. Nonetheless, xz has gained traction since then, and its

Bug#782550: mysql-server-5.5: Use /bin/bash instead of /bin/sh for mysqld_safe

I forgot to mention that this issue only applies to the Debian version of mysqld_safe (due to 38_scripts__mysqld_safe.sh__signals.patch). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#782540: dash: wait returns whenever a child process is stopped/continued

Package: dash Version: 0.5.7-4+b1 Severity: normal Control: affects -1 mysql-server-5.5 The wait builtin apparently returns immediately upon SIGCHLD, which means it will return prematurely if a child is stopped or continued: set +m sleep 1000 wait # This will return immediately if

Bug#782550: mysql-server-5.5: Use /bin/bash instead of /bin/sh for mysqld_safe

Package: mysql-server-5.5 Version: 5.5.41-0+wheezy1 Severity: wishlist Due to a bug in dash (#782540), mysqld_safe will kill and restart mysqld if the latter is stopped with SIGSTOP. Apparently, some VPSes throttle CPU usage by this mechanism. Hilarity ensues. Although this is not a bug in

Bug#782473: pdns-recursor: init.d script should provide the virtual facility $named

Package: pdns-recursor Version: 3.3-3+deb7u1 Severity: important [#585966 was marked as 'grave', but I don't have the guts for that. g] pdns-recursor may end up starting too late in the boot sequence, after packages which rely on a DNS server, due to the fact that it does not explicitly provide

Bug#377548: usbmount: Fails mounting some parts in a n-in-1 device

On Sat, Mar 14, 2015 at 11:25:36PM +0100, Hagen Fuchs wrote: Fixed. Tested and confirmed. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#781603: libssh2-1: changelog.gz is different between i386 and amd64 packages

On Wed, Apr 01, 2015 at 10:41:51PM +0200, Mikhail Gusarov wrote: $ wc -c */usr/share/doc/libssh2-1/changelog.gz 59923 amd64/usr/share/doc/libssh2-1/changelog.gz 60425 i386/usr/share/doc/libssh2-1/changelog.gz The amd64 version is the correct one. I'm actually unable to reproduce

Bug#781603: libssh2-1: changelog.gz is different between i386 and amd64 packages

Package: libssh2-1 Version: 1.5.0-2 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch Apparently, the different-gz-across-architectures bug strikes again: Preparing to unpack libssh2-1_1.5.0-2_i386.deb ... Unpacking libssh2-1:i386 (1.5.0-2) over (1.5.0-2)

Bug#779433: perl-modules: upgrade to perl-modules 5.20.2-1 breaks doc-base reconfiguration

severity 779433 important thanks On Sat, Feb 28, 2015 at 08:17:24AM -0600, Brian Paterni wrote: The 'PerlIO.pm' module it's looking for is installed to '/usr/share/perl/5.20.2/PerlIO.pm'. However '/usr/share/perl/5.20.2' does not seem to be a part of the @INC list. I was wondering why

Bug#377548: usbmount: Fails mounting some parts in a n-in-1 device

On Tue, Sep 30, 2014 at 04:52:08PM +0200, Hagen Fuchs wrote: I have a bugfix-branch of upstream, https://github.com/hfuchs/usbmount/tree/hfuchs.377548 This version has a bug, though: when plugging in a device, it will not run the scripts in /etc/usbmount/mount.d, outputting an error message

Bug#773282: mariadb-server-10.0: init script returns failure on success

Package: mariadb-server-10.0 Version: 10.0.15-2 Severity: normal Upgrading from 10.0.15-1 to -2: Setting up mariadb-server-10.0 (10.0.15-2) ... [ ok ] Stopping MariaDB database server: mysqld. [ ok ] Starting MariaDB database server: mysqld. invoke-rc.d: initscript mysql, action start

Bug#772603: imagemagick:amd64 installation fails with imagemagick-6.q16:i386

Package: imagemagick Version: 8:6.8.9.9-3 Severity: important [ CCing the submitter of #761836, which I'm guessing is the same bug. ] I'm getting an error when attempting to install/configure imagemagick: # dpkg --configure --pending Setting up imagemagick (8:6.8.9.9-3) ...

Bug#771549: fail2ban: init script refuses to start after a crash

Package: fail2ban Version: 0.9.1-1 Severity: normal I've had fail2ban segfaulting yesterday (in libsqlite3; probably not worth a bug report, since I couldn't reproduce it). Anyway, fail2ban is no longer running[*], so let's restart it: # service fail2ban start [] Starting authentication

Bug#771213: mariadb-server-10.0: file conflict with mysql-client-5.5

Package: mariadb-server-10.0 Severity: serious Here's me trying to migrate from MySQL to MariaDB: Unpacking mariadb-server-10.0 (10.0.14-4) ... dpkg: error processing archive /var/cache/apt/archives/mariadb-server-10.0_10.0.14-4_i386.deb (--unpack): trying to overwrite

Bug#764510: gcc-4.9: gnucash segfaults when built with GCC 4.9

reassign -1 gnucash found -1 found -1 1:2.6.4-1 tags -1 + patch thanks Maybe next time, I'll spend five minutes looking at the code instead of an evening messing around with gcc. (It was very formative, though. Thanks for your help. And sorry for wasting your time.) Reassigning this stack

Bug#764510: gcc-4.9: gnucash segfaults when built with GCC 4.9

[ I assumed the BTS would send a Cc to the gnucash maintainer due to the affects header, but that probably wasn't the case. Sorry, Sébastien. ] On Wed, Oct 08, 2014 at 08:25:05PM +0200, Matthias Klose wrote: are there any suspicious compiler warnings? maybe fix these first. -Werror -Wall

Bug#764510: gcc-4.9: gnucash segfaults when built with GCC 4.9

Package: gcc-4.9 Version: 4.9.1-16 Severity: important Control: affects -1 gnucash [ I'm probably filing this under the wrong package/severity; please reassign/adjust as you see fit. ] The current version of gnucash (1:2.6.4-1) repeatably segfaults upon launch (and entering one value), which

Bug#763893: gnubiff: crashes with Attempt to unlock mutex that was not locked

Package: gnubiff Version: 2.2.15-3 Severity: important Tags: patch This happened every time I tried to configure a mailbox, making gnudiff pretty much useless in my case, hence the severity. Attaching patch to fix what was obviously a typo. -- System Information: Debian Release: jessie/sid

Bug#763712: git: $GIT_CONFIG should either apply to all commands, or none at all

Package: git Version: 1:2.1.1-1 Severity: normal This kind of stuff caused me a lot of hair-pulling: $ git config core.abbrev 32 git log --pretty=oneline --abbrev-commit 89be foo Here's the source of the discrepancy: $ grep abbrev $GIT_CONFIG .git/config git.conf: abbrev=32

Bug#763542: chrony: logrotate config file triggers an Unrecognized command error

Package: chrony Version: 1.30-1 Severity: normal Tags: patch I finally tracked down where that weekly Unrecognized command email was coming from. :) Attaching patch for the trivial fix. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable')

Bug#377548: usbmount: Fails mounting some parts in a n-in-1 device

On Tue, Sep 30, 2014 at 04:52:08PM +0200, Hagen Fuchs wrote: I replaced all calls to utilities from 'lockfile-progs' by one to flock(1), I feel silly for not having been aware of that simple command. :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#763553: syntax/debcontrol.vim: Vcs-Git does not recognize https:// URLs

Package: vim-runtime Version: 2:7.4.430-1 Severity: normal File: /usr/share/vim/vim74/syntax/debcontrol.vim Tags: patch Here's the trivial patch. :) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Foreign

Bug#763556: syntax/robots.vim: Match allow directive in addition to disallow

Package: vim-runtime Version: 2:7.4.430-1 Severity: wishlist File: /usr/share/vim/vim74/syntax/robots.vim Tags: patch Here's a simple patch that does the job. I kept the changes to a minimum, piggy-backing on the Disallow keyword instead of creating another one -- hope that's okay. -- System

Bug#377548: Fails mounting some parts in a n-in-1 device

Yes, this is an old bug. :) If anyone is interested, here's my own solution to this problem; the idea is simply to add some randomness to the interval between locking attempts. In my experience with a 4-in-1 device, the first interval is scattered enough for all attempts to go through on the

  1   2   3   4   5   6   7   >