Bug#1037073: proot: New upstream version available: 5.4.0 - 2023-05-13

Package: proot Version: 5.1.0-1.3 Severity: normal Dear Maintainer, There's a new upstream version of proot with several fixes and enhancements. For example, proot 5.1.0 that's currently included doesn't recognize the statx() syscall, so "ls" doesn't work with it. -- System Information:

Bug#1036905: libdoxygen-filter-perl has new upstream version 1.73

Package: libdoxygen-filter-perl Version: 1.72-3 There's new upstream version with some support for subroutine signatures.

Bug#1017647: Update ucarp to current upstream version

Package: ucarp Version:1.5.2-2.2 There's newer version available at https://github.com/jedisct1/UCarp/ sadly still listed as 1.5.2 Among changes are the addition of --debug and --mcastip options, as well as some fixes. Please, consider updating.

Bug#886941: libproc-processtable-perl: Recognize the new P (parked) process state

Package: libproc-processtable-perl Version: 0.53-2+b2 Severity: normal Tags: upstream Dear Maintainer, There is a new process state with newer kernels: P (parked). It is intrudced there: https://lkml.org/lkml/2017/9/25/257 There's already fix in the upstream

Bug#883458: ucarp on vlan interfaces broken by ifupdown's recursion check

Package: ucarp Version: 1.5.2-2+b1 Severity: normal Dear Maintainer, There's new version of ifupdown in Debian Stretch that adds additional locking and recursion checks. Unfortunately, the way ucarp is currently integrated in /etc/network/ifu-up.d/ucarp is not compatible with the new

Bug#698218: roundcube-core: maybe remove obsolete entries from /e/r/htaccess?

2017-09-10 19:47 GMT+03:00 Sandro Knauß : > just for me to understand, you are asking for the default deactivated parts to > be updated? Or are you suggesting to enable them by default? Because from your > inital report you only mention deactivated lines: > #

Bug#870255: whois: Can't retrieve nameserver information

On 31.07.2017 17:47, Marco d'Itri wrote: On Jul 31, Teodor Milkov <t...@del.bg> wrote: Unfortunately nameserver queries do not work in 5.2.17, so I ended up using both old and new whois at the same time: This is a feature: if you want to query for a name server then you shou

Bug#870255: whois: Can't retrieve nameserver information

On 31.07.2017 14:02, Marco d'Itri wrote: On Jul 31, Teodor Milkov <t...@del.bg> wrote: Recently (past week?) something changed in the whois servers and we started to get much less information about domains. Fixed in 5.2.17, I will make a stable update later this week. Until then, you ca

Bug#870255: whois: Can't retrieve nameserver information

.239.32.10 Registrar: MarkMonitor Inc. Registrar WHOIS Server: whois.markmonitor.com Registrar URL: http://www.markmonitor.com >>> Last update of whois database: 2017-07-31T10:37:43Z <<< Best regards, Teodor -- System Information: Debian Release: stretch/sid

Bug#842718: closed by Osamu Aoki <os...@debian.org> (Bug#842718: fixed in maildrop 2.8.4-2)

/ would fix it and we are actually using it for more than 2 years already with locally compiled maildrop. Best regards, Teodor On 11.12.2016 07:51, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the maildrop package: #842718

Bug#844542: /sbin/writeboost doesn't work for static options (e.g. write_around_mode)

-disk123 failed: Invalid argument Command failed After the above error /write_around_mode=1/ is missing from the output of the /dmsetup table/ command. Please find attached a patch, which rectifies the problem for us. Best regards, Teodor --- writeboost.orig 2016-11-16 17:54:14.935717731 +0200

Bug#842718: maildrop: header add/match corruption bug with -A

Package: maildrop Version: 2.7.1-3 Severity: normal Dear Maintainer, There's a bug in the maildrop version currently in Jessie discussed here: http://courier-mail-server.10983.n7.nabble.com/Interesting-bug-failed-to-match-after-adding-headers-in-maildrop-td21606.html This bug is fixed with

Bug#644240: bat: ASSERT failure in QList::operator[]: "index out of range"

Hi, 2016-09-21 0:58 GMT+03:00 Carsten Leonhardt : > do you still have this problem with a current bacula version? I cannot test this anymore, from what I know they (old job) still use the old bacula version. I suppose you can close this bug. Thanks

Bug#838293: /sbin/writeboost uses deprecated blockdev --getsize

Package: writeboost Version: 1.20160718-1 Doesn't work with large devices. --getsize Print device size (32-bit!) in sectors. Deprecated in favor of the --getsz option. Best regards, Teodor

Bug#820328: perl: UTF-8 in regular expressions sometimes causing a crash

Package: perl Version: 5.20.2-3+deb8u4 Severity: normal Dear Maintainer, There's a bug introduced in Perl 5.20.2 involving UTF-8 in regular expressions and sometimes causing a crash has been fixed. It's fixed in 5.20.3. More information: https://rt.perl.org/Public/Bug/Display.html?id=124109

Bug#810799: libcgi-session-perl: Perl DSA-3441-1 exposes taint bug in CGI::Session::Driver::file

rn File::Spec->catfile($self->{Directory}, sprintf( $FileName, $sid )); } Best regards, Teodor On 15.01.2016 23:47, Niko Tyni wrote: Source: libcgi-session-perl Source-Version: 4.48-1+deb8u1 We believe that the bug you reported is fixed in the latest version of libcgi-session-perl, which is

Bug#786685: proftpd-basic: SSL / TLS handshakes for data connections sometimes stall for 3-30 seconds

Hi, This is affecting a lot of people. Also, there's new upstream bugfix release 1.3.5a addressing this issue. Please, consider applying the patch. Best regards.

Bug#789054: sudo: PERM_ROOT: setresuid(0, -1, -1): too many processes

Package: sudo Version: 1.8.5p2-1+nmu2 Severity: normal Tags: patch upstream Dear Maintainer, This is regression in upstream sudo, which is already fixed in official sudo repo. Long story short: a user with limited max user processes cannot sudo to root. For more details and discussion see:

Bug#751931: Not enabled by default

on a replacement function, but I would prefer not to. Talking with people over at ##php over at Freenode irc, it seems the issue is caused by a mismatch between how the main PHP code and the PECL PHP extension is compiled. Hope these nuggets of information help :) /Teo. -- Teodor Väänänen

Bug#698821: linux-image-3.2.0-4-amd64: ARECA driver arcmsr is out of date - please update

FTR, It seems newest areca driver is finally merged into vanilla kernel 3.18: http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/scsi/arcmsr/arcmsr_hba.c?id=b2776bf7149bddd1f4161f14f79520f17fc1d71d Unfortunately, neither Wheezy nor Jessie have support for 1214 and

Bug#774760: quagga: Support linux kernel 3.14 (CVE-2014-0181 netlink fix)

/8e998b1eb5fea53f2a2eddd9f7f2b8ab004406f3 Best regards, Teodor -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (x86_64) Kernel: Linux 3.2.65-grsec (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh

Bug#767742: linux-image-3.16.0-4-amd64: screen flickering with ATI Radeon X1600

Package: src:linux Version: 3.16.7-2 Followup-For: Bug #767742 Hi It appears that this problem affects multiple graphic cards that depend on the 'radeon' kernel module. Using 'nomodesetting' is not an option because the resolution gets too small (1024x768). On this laptop I still use the last

Bug#754294: Debian kernel fix for routing regression in 3.2.60

-local_df-tes.patch ../revert-net-ip-ipv6-handle-gso-skbs-in-forwarding-pat.patch dpkg -i linux-image-3.2.0-4-amd64_3.2.60-1+deb7u1a~test_i386.deb And then tried my usual download-from-windows-host test, which worked fine. Best regards, Teodor Milkov -- To UNSUBSCRIBE, email to debian-bugs-dist

Bug#754294: Regression: While routing Kernel chokes on spurious too big IP packets

I wonder if this is the same bug I've been experiencing? See it reported and discussed at the following places: https://bugzilla.kernel.org/show_bug.cgi?id=79891 http://www.spinics.net/lists/netdev/msg288798.html Best regards, Teodor -- To UNSUBSCRIBE, email to debian-bugs-dist-requ

Bug#748595: irqbalance: MSI interrupts found in /proc/interrupts but none found in sysfs (kernel version mismatch)

Package: irqbalance Version: 1.0.3-3 Severity: important Dear Maintainer, The combination of irqbalance version and linux kernel version included in Wheezy is not compatible as described in this upstream bug report: https://github.com/Irqbalance/irqbalance/issues/6 We had to downgrade to

Bug#707550: opu: package php-mdb2/2.5.0b2-1

Hi, 2014/1/21 intrigeri intrig...@debian.org: Hi, Teodor, ping? I don't have the necessary experience to make this source debdiff. Thomas, are you still interested in uploading this (simple) patch for squeeze? Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#716762: [buildd-tools-devel] Bug#716762: sbuild maybe should end the session after package build?

Hi, 2013/7/13 Roger Leigh rle...@codelibre.net: On Fri, Jul 12, 2013 at 03:15:05PM +0300, Teodor wrote: I've noticed that after upgrade to Debian 7, sbuild doesn't end the schroot session anymore. This is confirmed by the log too: | Not removing build depends: as requested This bug report

Bug#716762: sbuild maybe should end the session after package build?

Package: sbuild Version: 0.63.2-1.1 Severity: minor Hi, I've noticed that after upgrade to Debian 7, sbuild doesn't end the schroot session anymore. This is confirmed by the log too: | Not removing build depends: as requested | Keeping session: wheezy-amd64-sbuild-... This is not consistent

Bug#714854: spamass-milter: race condition at boot with spamd

Package: spamass-milter Version: 0.3.1-10 Severity: normal Hi, Sometimes spamass-milter fails to start at boot because spamd is down, more concrete spamd is started *after* spamass-milter. I've seen then only 3 times in 5 years. :-) Adding this to the init script should eliminate the race

Bug#714745: unattended-upgrades: doesn't upgrade pkgs from backports if NEW pkg dependencies

Package: unattended-upgrades Version: 0.79.5 Severity: normal Hi, I've configured u-a to upgrade from wheezy-backports with: Unattended-Upgrade::Origins-Pattern { .. o=Debian\ Backports,a=wheezy-backports; } (and Pin-Priority: 500 for all packages in the w-bpo archive) However, the

Bug#697357: bridging broken over bond interfaces

:3.2.10-k == While this one from sourceforge works: == # modinfo tmp/igb-3.4.7.ko |grep ^version: version:3.4.7 == HTH -- Teodor Milkov | System Administrator | ICDSoft Ltd. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject

Bug#711826: no more unattended upgrades since Wheezy is out

2013/6/14 Harald Dunkel ha...@afaics.de: Changing config files for 1 or 2 PCs is not the problem. The problem is, that its not unattended anymore. I have to access appr. 150 servers, desktops and laptops to make this work again. Thats a lot of work for a package that promised to do its job

Bug#711826: no more unattended upgrades since Wheezy is out

2013/6/10 Harald Dunkel harald.dun...@aixigo.de: Since Wheezy is out the unattended-upgrades for Squeeze don't work anymore. The default configuration in /etc/apt/apt.conf.d/50unattended-upgrades says Unattended-Upgrade::Allowed-Origins { ${distro_id} stable; stable == wheezy now,

Bug#711037: zabbix-server-mysql: proc.num[spamd].last(0) always at 0

Hi, 2013/6/7 Craig Small csm...@debian.org: I'm the procps maintainer (Debian and upstream). Dmitry asked me to have a look at this bug as pgrep was discussed. My first impression is that there is some confusion between command line and process name. Digging deeper, that is the correct

Bug#711037: zabbix-server-mysql: proc.num[spamd].last(0) always at 0

2013/6/5 Dmitry Smirnov only...@member.fsf.org: `pgrep` is searching for substring in process name. For example if I have `konsole` running the `pgrep konso` will return PID even though there is no process konso running. proc.num is checking for exact process name so it will return 0 for

Bug#711037: zabbix-agent: proc.num[spamd].last(0) always at 0

Hi, 2013/6/5 Dmitry Smirnov only...@member.fsf.org: `pgrep --exact spamd | wc -l` or `pgrep --count --exact spamd` would be an equivalent of `zabbix_get -s localhost -k 'proc.num[spamd]'` Weird, not even 'pgrep' can count them even if 'spamd' is running. This might have the same

Bug#711037: zabbix-server-mysql: proc.num[spamd].last(0) always at 0

Package: zabbix-server-mysql Version: 1:2.0.6+dfsg-1 Severity: normal (real version is ~bpo70+1) Hi, The proc.num[spamd] always reports 0, web frontend or command line: | root@return:~# zabbix_get -s localhost -k 'proc.num[spamd]' | 0 | root@return:~# zabbix_get -s localhost -k

Bug#710571: Patch for /lib/lsb/init-functions

2013/6/3 Didier 'OdyX' Raboud o...@debian.org: I have now also re-read the #683654 bugreport and got more convinced that changing these logging functions is a really bad idea. The biggest blocker that I see is the output that one gets when managing services by hand: if one setups VERBOSE=no in

Bug#710571: Patch for /lib/lsb/init-functions

This topic was discussed with LSB maintainers on #683654. Maybe these two bugs should be merged, but I don't know if the discussion will be preserved. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683654 2013/6/1 Josh Triplett j...@joshtriplett.org: The attached git patch makes the log_*

Bug#696332: lsb-release: release/codename depend on a successful apt-get

Control: block 685355 by 696332 2013/5/21 Didier 'OdyX' Raboud o...@debian.org: Even if your log confirms that, I can't reproduce this behaviour on jessie. I cant test on „jessie/testing” but this affects at least unattended-upgrades on „wheezy/stable”. See bug #685355 for details. Cheers --

Bug#708238: bacula-director-pgsql: Fatal error: Version error for database bacula. Wanted 14, got 12

Package: bacula-director-pgsql Version: 5.2.6+dfsg-9 Severity: grave Hi, I've upgraded from Debian 6.0 to Debian 7.0 and Bacula director does not start after upgrade. It appears that the database was not upgraded: | 14-May 14:24 bacula-dir JobId 0: Fatal error: Version error for | database

Bug#707550: opu: package php-mdb2/2.5.0b2-1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: opu Hi, This is a follow up on one email thread from debian-release list: http://lists.debian.org/debian-release/2012/05/msg00182.html Please apply the attached patch to php-mdb2 package

Bug#676660: radicale: please package new upstream version 0.7.1

Package: radicale Version: 0.7-1.1 Severity: wishlist Hi, Please package version 0.7.1 for the following reasons: - [acl/IMAP.py] adds IMAP authentication module - [acl/PAM.py] fix PAM group membership check - [acl/courier.py] some fixes for courier auth Unfortunately, PAM auth will still

Bug#652719: unattended-upgrades: unexpected daily conffile prompt messages from Cron

I would like to close this report, but I don't know on which version it was fixed. Michael, if you can determine that from the bzr repo history, please close this report with the correct version number. From my point of view the problem appears to be fixed a long time ago. 2013/3/13 Tomas

Bug#702547: unblock: unattended-upgrades/0.79.5

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package unattended-upgrades. It contains one important fix: * unattended-upgrade: - do not nice/ionice as this wil affect daemon restarts (closes: #701850)

Bug#702509: unattended-upgrades: does not run autonomously, even after it was enabled

control: -1 severity normal 2013/3/8 Arturo Moral amo...@gmail.com: This config was removed in version 0.79.5 and might not work at all: I'm currently using 0.79.4, therefore the config change does not affect me, right? You should not use it, 0.79.5 will migrate to testing on the following

Bug#702509: unattended-upgrades: does not run autonomously, even after it was enabled

2013/3/7 g0to amo...@gmail.com: -- Configuration Files: /etc/apt/apt.conf.d/50unattended-upgrades changed: // Automatically upgrade packages from these origin patterns Unattended-Upgrade::Origins-Pattern { // Codename based matching: // This will follow the migration of a

Bug#702323: unattended-upgrades: logrotate should not rotate u-a-dpkg* files

Package: unattended-upgrades Version: 0.79.5 Severity: minor Hi, Recently the logrotate.d file was updated to rotate all files: /var/log/unattended-upgrades/unattended-upgrades*.log This has an undesired effect to rotate also all unattended-upgrades-dpkg_*.log files with NAME.1.gz and

Bug#702325: unattended-upgrades: false apache2 upgradable but kept back

Package: unattended-upgrades Version: 0.79.3 Severity: normal Hi, I've only seen this in the past (and today) for apache2 package: | Packages that are upgraded: | apache2-mpm-prefork apache2-utils apache2.2-bin apache2.2-common | Packages with upgradable origin but kept back: | apache2 U-A

Bug#702150: dctrl-tools: -X should match on NAME (VERSION) too

Package: dctrl-tools Version: 2.22.2 Severity: important Hi, First, this cannot be always reproduced just because »apt-cache dumpavail« doesn't give the same content on successive executions. I'm using this command to add package pins, for example for python2.7: apt-cache dumpavail |

Bug#702150: [Dctrl-tools-devel] Bug#702150: dctrl-tools: -X should match on NAME (VERSION) too

2013/3/3 Antti-Juhani Kaijanaho antti-juh...@kaijanaho.fi By using '-X' some times not all packages are selected: Package: python2.7 Source: python2.7 (2.7.3-7) This is the expected result, hence downgrading to wishlist. -X is supposed to check if the field in question (in this

Bug#701961: clusterssh: does not follow .ssh/config anymore

Package: clusterssh Version: 4.01.04-1 Severity: important Hi, This is a big regression from previous version (4.01.01). I have per host configuration in .ssh/config for default user name. In cssh clusters file I only add the hostnames. With the current version (4.01.04) it tries to connect

Bug#699794: [Popcon-developers] Bug#699794: Bug#699794: popularity-contest: should work without a local SMTP/sendmail

2013/2/5 Petter Reinholdtsen p...@hungry.com: It should try to connect to popcon.debian.org. See SUBMITURLS in /usr/share/popularity-contest/default.conf for the default URLs, and /etc/cron.daily/popularity-contest for the program deciding how to submit the information. Looking at that

Bug#699794: [Popcon-developers] Bug#699794: popularity-contest: should work without a local SMTP/sendmail

2013/2/5 Petter Reinholdtsen p...@hungry.com: popcon work without SMTP. It will first try using http for delivery, and only if this fail will it try to send email. If http delivery fail, it will syslog a message about this. That would be great. However, I've seen this fail both from my work

Bug#699794: popularity-contest: should work without a local SMTP/sendmail

Package: popularity-contest Version: 1.56 Severity: wishlist Hi, After removing postfix (or any other SMTP server) from all systems, I see that the monthly popcon message fails to be delivered (no IP addr based relay here, only u/p submission). It would be nice if popcon could work just like

Bug#699149: bacula-fd: should not run as 'root' by default

2013/1/31 Alexander Golovko alexan...@ankalagon.ru: You lose files owner/group and acl on restoring. That's not a big deal comparing with the increased security. /e/d/bacula-{dir,sd} has nonempty ARGS and bacula-{director,sd} will be incorrectly runned under root privileges if defaults file

Bug#699442: fail2ban: please add configuration for roundcube

Package: fail2ban Version: 0.8.6-3wheezy1 Severity: wishlist Hi, Please add /etc/fail2ban/filter.d/roundcube.conf with this content: | [Definition] | | failregex = FAILED login for .*. from HOST | ignoreregex = Also, an entry to jail.conf disabled by default would be nice: | [roundcube] |

Bug#699442: fail2ban: please add configuration for roundcube

2013/1/31 Yaroslav Halchenko deb...@onerussian.com: would you mind also providing sample log lines demonstrating this failed attempts? These are like this: [22-Jan-2013 22:28:21 +0200]: FAILED login for user1 from 109.97.x.x [23-Jan-2013 12:53:09 +0200]: FAILED login for user2 from 79.117.x.x

Bug#699149: [pkg-bacula-devel] Bug#699149: bacula-fd: should not run as 'root' by default

2013/1/29 Alexander Golovko alexan...@ankalagon.ru: ARGS=-u bacula -g bacula -k I think that from a security perspective this should be the default on package installation. This will lead to impossibility to restore backups without restarting bacula-fd. This is also can require changing

Bug#699149: bacula-fd: should not run as 'root' by default

Package: bacula-fd Version: 5.2.6+dfsg-7 Severity: normal Hi, The other Bacula services are started by 'bacula' user. Only bacula-fd is started as 'root'. However, I've just discovered that it can function properly with limited privileges too. For this one must edit /etc/default/bacula-df to

Bug#620825: bacula-director-common: wrong email From address

Hi, I'm using this configuration in Messages: mailcommand = /usr/sbin/bsmtp -h SMTPHOST -f \Bacula \bac...@host.domain.tld\\ -s [..] The main reason is to have the real address instead of the fake %r which could be rejected at the destination. This same address is added automatically by

Bug#699173: bsmtp: missing Message-Id: header on notifications

Package: bacula-common Version: 5.2.6+dfsg-7 Severity: normal Hi, I've noticed that Message-Id: header is missing on notifications. This could cause the notifications to be rejected by some SMTP servers. Cheers -- System Information: Debian Release: 7.0 APT prefers testing APT policy:

Bug#698947: bacula-fd: Messages:append to local log file is ignored

Package: bacula-fd Version: 5.2.6+dfsg-7 Severity: normal Hi, I'm trying to keep logs on the local system. For this I've put this configuration in /etc/bacula/bacula-fd.conf: Messages { Name = Standard append = /var/lib/bacula/log = all director = BACULAMASTER-dir = all,

Bug#493092: bacula: package upgrade creates or modifies `bacula-*.conf.dist'

Package: bacula-fd Version: 5.2.6+dfsg-7 Followup-For: Bug #493092 Hi, Packages upgraded yesterday: bacula-common:amd64 5.2.6+dfsg-2 = 5.2.6+dfsg-7 bacula-fd:amd64 5.2.6+dfsg-2 = 5.2.6+dfsg-7 The packages were installed last week. After upgrade I've got a new file

Bug#695610: opendkim: fails to configure

Hi Scott, 2013/1/7 gustavo panizzo gfa g...@zumbi.com.ar: i have opendkim installed, but disabled at boot time (update-rc.d opendkim disable). when the packages gets upgraded, i got that error. this problem only appears on my laptop, where i keep opendkim installed but not running (for

Bug#687602: retext: should restore the window position and size at startup

2013/1/12 Dmitry Shachnev mity...@gmail.com: Hm, I probably was not clear enough: you need to add saveWindowGeometry=true (w/o quotes) to ~/.config/ReText project/ReText.conf to get that working. See https://sourceforge.net/p/retext/wiki/Configuration%20file/ for details. Thanks for this

Bug#694046: bacula-common: missing 'create' directive in logrotate.d/bacula-common

2012/11/23 Teodor mteo...@gmail.com: Please improve /etc/logrotate.d/bacula-common file with: /var/log/bacula/log { create 0644 bacula bacula Actually, the group should be 'adm' and no read permissions for others: create 0640 bacula adm Cheers -- To UNSUBSCRIBE, email to debian-bugs

Bug#698218: roundcube-core: maybe remove obsolete entries from /e/r/htaccess?

2013/1/15 Vincent Bernat ber...@debian.org: We are shipping htaccess as shipped by upstream. I see little reason to change it just because they may be obsolete but harmless. Note that the first one is not commented by default. Using the files from upstream is always a good idea. But again some

Bug#698218: roundcube-core: maybe remove obsolete entries from /e/r/htaccess?

Package: roundcube Version: 0.7.2-5 Severity: minor Hi, I'm using roundcube v0.7.x on both Debian 6.0 and 7.0 systems. I see that these entries are still there although I've never found a technical reason to keep them on my setup: # http://bugs.php.net/bug.php?id=30766 #php_value

Bug#698223: roundcube-plugins: plugin show_additional_headers should be configured in /e/r/plugins

Package: roundcube Version: 0.7.2-5 Severity: wishlist Hi, The plugin show_additional_headers is not like all other plugins. To be able to use it one must add it's config in main.inc.php. | # plugin: show_additional_headers | $rcmail_config['show_additional_headers'] = array('Reply-To', ..);

Bug#687602: retext: should restore the window position and size at startup

Package: retext Version: 4.0.0-1 Followup-For: Bug #687602 Hi, I've installed the latest version from experimental and I still see that these window properties are not preserved. Cheers -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (500,

Bug#697758: dovecot-core: starting up log message should have the same priority stop does

Package: dovecot-core Version: 1:2.1.7-6 Severity: minor Hi, I've noticed these entries in syslog (mail.info): | Jan 9 04:33:15 palomino dovecot: master: Warning: Killed with | signal 15 (by pid=1037 uid=0 code=kill) | Jan 09 04:33:15 master: Info: Dovecot v2.1.7 starting up (core | dumps

Bug#697760: dovecot-core: ssl_cert/key should be specific to each protocol

Package: dovecot-core Version: 1:2.1.7-6 Severity: wishlist Hi, It appears that these settings are common for all protocols: ssl_cert = /etc/ssl/certs/imap.DOMAIN.crt ssl_key = /etc/ssl/private/imap.DOMAIN.key I would like to set different hostnames (and IP addresses) for IMAP and

Bug#693114: dovecot-core: Mailboxes inaccessible after upgrade

Hi, Considering that mailbox auto detection is not always working, I recommend to just add a big NEWS entry telling people to manually set the 'mail_location' parameter in /etc/dovecot/local.conf. I've always set this parameter manually, but after reading how much problems it could cause I

Bug#697769: dovecot-core: please setup 'lda' by default during installation

Package: dovecot-core Version: 1:2.1.7-6 Severity: wishlist Hi, Because 'dovecot-lda' is „special” I've setup the following to make it work with Postfix securely without 'sudo' of setuid root: 1) info_log path set to a world writable file: # conf.d/15-lda.conf protocol lda {

Bug#697583: opendkim: reports insecure key in all AR headers

Package: opendkim Version: 2.6.8-3 Severity: normal Hi, I've done multiple tests and both 1024 and 2048-bit keys ar reported insecure key in the Authentication-Results: header. | Authentication-Results: smtp.DOMAIN; dkim=pass | reason=2048-bit key; insecure key | header.d=gmail.com

Bug#695145: opendkim: DKIM signature verification is failing

Obviously DKIM signature verification works in most cases (including for gmail). Looking at this report it seems that DKIM does not fail signature verification, but only the log message is wrong. Do you agree? In this case the one-line patch could be included in an upload for an important fix

Bug#695610: opendkim: fails to configure

Hi, I've installed opendkim a few days ago and didn't encounter this problem. Why your directory was missing at package installation? Did you manually remove it? This could be a potential problem at boot but I've just tested and the directory is correctly handled at boot. Cheers -- To

Bug#696856: spamass-milter: Could not retrieve sendmail macro i

2012/12/28 Teodor mteo...@gmail.com: | Dec 28 03:07:07 palomino spamass-milter[30692]: Could not retrieve | sendmail macro i!. I've found some related info on the MILTER_README: http://www.postfix.org/MILTER_README.html#workarounds Quoting from that page: current versions of dkim-filter

Bug#696856: spamass-milter: Could not retrieve sendmail macro i

Package: spamass-milter Version: 0.3.2-1 Severity: normal Hi, After spamass-milter service restart and the first message received, these lines are found in the syslog: | Dec 28 03:07:07 palomino spamass-milter[30692]: Could not retrieve | sendmail macro i!. Please add it to

Bug#696861: spamass-milter: must create an empty home directory

Package: spamass-milter Version: 0.3.2-1 Severity: normal Hi, During package installation the account is created without HOME: | Not creating home directory `/var/lib/spamass-milter'. But, on all messages received you'll see many messages like this: | Dec 27 09:25:13 palomino spamd[13761]:

Bug#695301: openvpn: Fails to install a logrotate.d entry

2012/12/6 Alberto Gonzalez Iniesta a...@inittab.org: As far as I know, openvpn does not create that log file, unless you told it to. In that case, it's not a bug in the package... That's my experience too. By default 'openvpn' will log to /var/log/syslog which is handled automatically. If

Bug#695301: openvpn: Fails to install a logrotate.d entry

2012/12/7 Karl Schmidt k...@xtronics.com: IMO it probably should be set up to log out-of-the-box as well [..] It does log by default to /var/log/syslog on Linux. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#605449: Set up for bacula-director-pgsql runs before that of postgresql-8.4.

Package: bacula-director-common Version: 5.2.6+dfsg-6 Hi, Indeed, any SQL backend (postgresql, mysql ..) does not have to be local. But in case it is local (as I and many probably have) this needs to be declared correctly in the init script: #! /bin/sh ### BEGIN INIT INFO # Provides:

Bug#694046: bacula-common: missing 'create' directive in logrotate.d/bacula-common

Package: bacula-common Version: 5.2.6+dfsg-6 Severity: normal Hi, Please improve /etc/logrotate.d/bacula-common file with: /var/log/bacula/log { create 0644 bacula bacula compress delaycompress missingok notifempty rotate 12 monthly } The most important is create directive since

Bug#693744: libnetcf1: uninstallable due to Conflicts: libvirt0 (= 0.10.1-2~)

severity 693744 serious stop root@frost:~# aptitude full-upgrade The following packages will be upgraded: libnetcf1{b} 1 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 51.6 kB of archives. After unpacking 3,072 B will be freed. The following packages have

Bug#693132: initscripts: mountnfs fails at boot if $NFSHOST is present on /etc/hosts

2012/11/13 Roger Leigh rle...@codelibre.net: This is a symptom of a bug in the -bootclean scripts; I'll be fixing this soon with a new upload of sysvinit. The problem I reported is for Debian Linux 6.0.6 systems, not current Wheezy. So, it doesn't appear to be the same problem as the one

Bug#693132: initscripts: mountnfs fails at boot if $NFSHOST is present on /etc/hosts

Package: initscripts Version: 2.88dsf-13.1+squeeze1 Severity: normal Hi, After testing NFS on four Debian hosts I've found that the presence of a static entry for the NFSHOST will make mountnfs to fail at boot. Ironically, I've added the static entry just to make it more reliable. :-)_ The one

Bug#693132: initscripts: mountnfs fails at boot if $NFSHOST is present on /etc/hosts

2012/11/13 Teodor mteo...@gmail.com: [..] script /etc/init.d/mountnfs.sh appears to be a no-op I've just tested and after removal of '/etc/init.d/mountnfs.sh' and '/etc/init.d/mountnfs-bootclean.sh' from the init sequence (with update-rc.d remove) I can confirm that the NFS mounting

Bug#692448: qemu: system crash on 'libaio1' removal

Package: qemu Version: 0.12.5+dfsg-3squeeze2 Severity: serious Hi, I've just had a system crash a few seconds after I removed 'libaio1 package (declared orphan by deborphan). On KVM systems this is not a problem because its a dependency of qemu-kvm. But on Xen systems (+libvirtd) this package is

Bug#692448: qemu: system crash on 'libaio1' removal

2012/11/6 Michael Tokarev m...@tls.msk.ru: On 06.11.2012 15:40, Teodor wrote: I've just had a system crash a few seconds after I removed 'libaio1 package (declared orphan by deborphan). What kind of crash? Crash of what, exactly? What you were running? Debian Linux 6.0 (amd64) on top

Bug#692448: qemu: system crash on 'libaio1' removal

2012/11/6 Michael Tokarev m...@tls.msk.ru: So, can you start it again when libaio1 is NOT installed? Yes, I was able to start the VMs again after the libaio1 removal. I'm not sure about the full Xen system -- I can't test now. Cheers -- To UNSUBSCRIBE, email to

Bug#678506: consolekit: Rejected send message: type=method_call, interface=org.freedesktop.DBus.Properties

tags 678506 +patch quit I've been using this patch for more than two months to fix this noise in the logs. Please include it in Debian 7.0. Cheers --- ConsoleKit.conf 2012-03-01 00:26:35.0 +0200 +++ /etc/dbus-1/system.d/ConsoleKit.conf2012-08-11 12:30:28.084999148 +0300

Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev 12

Package: ethtool Version: 1:2.6.34-3 Severity: normal Tags: upstream Hi, On Broadcom NX II rev 12 network interfaces it's not possible to activate WoL using 'ethtool' (it can only be done from the MBA Configuration Menu). However, even if Pre-boot Wake On LAN was enabled 'ethtool' doesn't see

Bug#690845: ethtool: incorrect WoL detection on Broadcom NX II rev 12

2012/10/18 Ben Hutchings b...@decadent.org.uk: ethtool just reports what the driver tells it, so this isn't an ethtool bug. I thought this might be a driver problem just like setting WoL is not supported by the driver for rev 12 on these cards. Which kernel version are you using (package

Bug#690535: tftpd-hpa: fails to start if kernel flag ipv6.disable=1 is set

Package: tftpd-hpa Version: 5.0-18 Severity: important Hi, I've disables IPv6 via ipv6.disable=1 boot parameter. On all servers with this configuration tftpd-hpa doesn't start and prints in syslog: | in.tftpd[5303]: cannot open IPv6 socket, disable IPv6: Address family | not supported by

Bug#690158: ettercap: unconditionally sets net.ipv4.ip_forward=0

2012/10/12 Simon Paillard spaill...@debian.org: On top of that, ettercap is designed for man in the middle attacks, disabling kernel forwarding seems to be a must. man ettercap: NAME ettercap - multipurpose sniffer/content filter for man in the middle attacks Ok, good to know.

Bug#690158: ettercap: unconditionally sets net.ipv4.ip_forward=0

Package: ettercap Version: 1:0.7.3-2.1 Severity: grave Justification: causes non-serious data loss Hi, I've just found that running 'ettercap' on gateway system (were ip_forward is a must) will unconditionally disable the kernel flag. This affects both Debian 6.0 (squeeze) and Debian 7.0

Bug#682481: gnome-shell: epiphany shouldn't be the default browser

Didn't you forgot to add | www-browser in the Depends: line? Funny upgrade today with 121 new packages although I have at least two packages installed that provide www-browser. Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble?

Bug#668354: Downgrading

2012/9/19 Marcin Owsiany porri...@debian.org: severity 668354 wishlist thanks I had a look at LSB and it agrees with Debian policy in that it also requires calling a command rather than manipulating symlinks directly. [..] That's the requirement for Debian packages only. Also,

  1   2   3   4   5   6   7   >