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#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#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 is

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#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#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#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#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#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#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

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#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#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

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#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#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#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#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

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 is by

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 of

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

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#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#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,

Bug#668354: /etc/rcN.d/[SK]* symlinks are ignored if not mentioned on the /etc/init.d/.depend.* TARGETS

2012/9/19 Marcin Owsiany porri...@debian.org: AFAICT the issue is that: - muse creates symlinks in /etc/rcN.d directly, rather than using update-rc.d, thus insserv never learns about it, - when insserv is installed and not explicitly disabled, the symlinks are completely ignored No,

Bug#668354: /etc/rcN.d/[SK]* symlinks are ignored if not mentioned on the /etc/init.d/.depend.* TARGETS

reassign 668354 sysvinit-utils retitle 668354 /etc/rcN.d/[SK]* symlinks are ignored if not mentioned on TARGETS stop 2012/9/20 Petter Reinholdtsen p...@hungry.com: [Teodor MICU] The bug is that the boot process should not depend on the insserv internals (/etc/init.d/.depend.*). You have a S/K

Bug#685355: KeyError: 'CODENAME'

Since I had this problem only on my workstation, I have found that the cause was the network being down at the time Cron jobs were executed -- including u-a. Yesterday, I've added a short python script to /etc/cron.hourly that sent a nice message every hour: | /etc/cron.hourly/unattended-upgrade:

Bug#668354: [Pkg-sysvinit-devel] Bug#668354: sysv-rc: doesn't start service at boot due to high S98 number

Package: sysv-rc Version: 2.88dsf-22.1 First, this problem is present in Debian Linux 7.0 (wheezy). Second, the sequence numbers does NOT matter. The only thing that made a difference was to execute update-rc.d twice (name remove + defaults). Any idea why adding these symlinks manually (K02 +

Bug#668354: [Pkg-sysvinit-devel] Bug#668354: sysv-rc: doesn't start service at boot due to high S98 number

severity 668354 serious stop 2012/8/24 Teodor MICU mteo...@gmail.com: Any idea why adding these symlinks manually (K02 + S98) is not enough? What other action(s) does 'update-rc.d name defaults' do? It just adds/removes entries from «/etc/init.d/.depend.*» internal files. So, the init system

Bug#685355: KeyError: 'CODENAME'

2012/8/21 Michael Vogt m...@debian.org: Its confusing that it only fails inside cron, could you please add a line: print lsb_release.get_distro_information() before line 56 (i.e. before the failure) to see what the get_distro_information() call returns inside cron (and also outside of it)?

Bug#683654: lsb-base: some messages should be conditioned by $VERBOSE

2012/8/8 Didier 'OdyX' Raboud o...@debian.org: Le jeudi, 2 août 2012 16.38:41, Teodor a écrit : In Debian the recommendation for all init scripts is to check the variable VERBOSE from /etc/default/rcS and only print a message on console only if this variable is not 0. From the content of the

Bug#684152: [Pkg-freeipmi-devel] Bug#684152: freeipmi-tools: ipmimonitoring false critical alerts

2012/8/7 Yaroslav Halchenko deb...@onerussian.com: so this is a Debian squeeze -- stable ... and it is quite aged by now, even if we manage to figure out the source of the problem not sure if it would warrant an upload to stable. would you mind giving a try to a backport of a version from

Bug#682844: unattended-upgrades: squeeze should be replaced with wheezy

One more thing I noticed after I installed 0.79.2 is a missing ';' at the end of this line: -//Unattended-Upgrade::Mail root +Unattended-Upgrade::Mail root; Cheers -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#654851: unattended-upgrades: email notifications don't have Content-Type: header

Hi, There is an empty line between the headers that causes some headers (including Subject:) to be considered part of the message body. | From: root root@frost.DOMAIN | Date: Fri, 13 Jul 2012 09:48:04 +0300 | To: root@DOMAIN | Message-Id: 20120713064805.003CC179A9@mail.DOMAIN | | MIME-Version:

Bug#654851: unattended-upgrades: email notifications don't have Content-Type: header

2012/7/13 Michael Vogt m...@debian.org: Indeed, sorry for that, should be fixed in bzr trunk, if testing goes well I will upload today. It will use sendmail if available to set the header and if not mail but without the header as there is no portable way apparently to do that with mailx.

Bug#654851: unattended-upgrades: email notifications don't have Content-Type: header

2012/7/13 Teodor MICU mteo...@gmail.com: What if «mail» is not available either? I've just tested and no message is send. This is indeed mentioned in the configuration file (from apt.conf.d) but it should be updated to mention «sendmail» or «mailx» due to these changes. Probably a note in README

Bug#680482: libapache2-modsecurity: should not include all *.conf files by default

2012/7/6 Alberto Gonzalez Iniesta a...@inittab.org: If you want rules only for a VirtualHost, they can be added to its configuration file. You don't need to use /etc/modsecurity at all. Yes, but that's exactly the purpose of this directory. I don't really see the problem or the severity of

Bug#680917: roundcube-core: Symbolic link not allowed or link target not accessible: js/jquery-ui.min.js

2012/7/9 Vincent Bernat ber...@debian.org: ❦ 9 juillet 2012 10:14 CEST, Teodor mteo...@gmail.com : The reason for this broken links is that ../../../javascript get resolved to /var/lib/javascript but the correct location is /usr/share/javascript. Hi Teodor! Hi! We already got a similar

Bug#679928: systemd: PAM adding faulty module: pam_systemd.so

2012/7/9 Michael Biebl bi...@debian.org: Teodor, could you attach the output of debconf-show libpam-runtime please. Do you remember editing /etc/pam.d/common-session by hand? No, I don't think that's the case as showed in a previous message were a manual execution works properly. The issue is

Bug#679928: systemd: PAM adding faulty module: pam_systemd.so

2012/7/9 Tollef Fog Heen tfh...@err.no: I think what might have happened is an aborted upgrade, which I don't think we currently handle correctly. I'll have to take a look at the code in question, though. My guess is that this problem was caused by a deadlock in the upgrade. The packages were

Bug#679062: cron: should remove obsolete /etc/cron.daily/standard

2012/7/6 Javier Fernández-Sanguino Peña j...@computer.org: I'm not sure this is entirely's cron fault. From the subject: it looks like anacron is trying to run the old cron.daily's standard task. Could you please do this: - send the list of files under /etc/cron.daily/ - check if anacron is

Bug#680482: libapache2-modsecurity: should not include all *.conf files by default

2012/7/6 Alberto Gonzalez Iniesta a...@inittab.org: I'm proposing to remove the second paragraph completely because from my experince enabling all these rules for all web sites will cause too much noise in the log (like 99.9%) with entries like this: enabling all these rules ??? Which

Bug#679062: cron: should remove obsolete /etc/cron.daily/standard

reopen 679062 stop This process is not complete since I get this email from all systems where I upgraded cron: | Subject: Anacron job 'cron.daily' on frost.museglobal.ro | [..] | run-parts: failed to stat component /etc/cron.daily/standard: No such file or directory Cheers -- To

Bug#679728: systemd: diversion removed in postinst, should be removed in preinst

2012/7/2 Tollef Fog Heen tfh...@err.no: That's quite odd. Can you please provide the output of «grep systemd /var/log/dpkg.log»? See below. I've reinstalled «systemd» this morning on my workstation. Cheers -- 2012-07-02 10:55:30 upgrade systemd-gui:i386 44-2 44-3 2012-07-02 10:55:30

Bug#679928: systemd: PAM adding faulty module: pam_systemd.so

2012/7/2 Tollef Fog Heen tfh...@err.no: I suspect you have told pam that you want to manage common-session by hand, else this is a bug in pam-auth-update, since the postinst just says: if [ $1 = remove ] ; then pam-auth-update --package --remove systemd fi Can you please verify? I

Bug#679728: systemd: diversion removed in postinst, should be removed in preinst

2012/7/3 Tollef Fog Heen tfh...@err.no: Ah, it looks like it never actually got to the configure step of systemd. Does that sound correct, and is the diversion correctly removed now? If not, could you please try downgrading to 44-2 and then upgrading and verifying that the diversion is gone?

Bug#679728: systemd: diversion removed in postinst, should be removed in preinst

Diversion is not removed at all on package removal: | root@frost:~# ls -hl /lib/lsb/ | total 16K | drwxr-xr-x 2 root root 4.0K Jul 2 11:11 init-functions.d | -rw-r--r-- 1 root root 12K May 30 17:01 init-functions.systemd | root@frost:~# dpkg -S /lib/lsb/init-functions.d | lsb-base:

Bug#679728: systemd: diversion removed in postinst, should be removed in preinst

2012/7/2 Tollef Fog Heen tfh...@err.no: Did you upgrade to 44-3 before removing it or not? Yes, I've upgraded almost all packages (including systemd) and then reported Bug#679873: lsb-base: Can't open /lib/lsb/init-functions. Later I've uninstalled systemd packages to work around the problem,

Bug#663964: apt-listbugs?

Hi Michael, I believe this is a nice new function to have in U-A, but it's probably too late for wheezy. :-) 2012/6/28 Michael Vogt michael.v...@gmail.com: thanks for your bugreport. How does apt-listbugs put a package into this state? u-n should supoprt the dpkg HOLD state and honor that.

Bug#677508: gnome-terminal: received signal SIGSEGV in g_object_notify kills all terminals

2012/6/24 Josselin Mouette j...@debian.org: Thanks for the backtrace. However it is not usable per se. Could you install debugging symbols for gtk3 and vte, and try again? I've installed some additional gtk3 debug packages (libgtk-3-0-dbg was already installed). However, I cannot find any vte

Bug#678030: unattended-upgrades: No 'fancy' output init.d script

reopen 678030 stop 2012/6/19 Michael Vogt m...@debian.org: Thanks a lot! I updated bzr to include your version with some small modifications. Looking at the README.Debian.gz from lsb-base it appears that log_action_begin_msg and log_action_end_msg is actually closer to what we want as the

Bug#678030: unattended-upgrades: No 'fancy' output init.d script

2012/6/18 Kees de Jong keesdej...@gmail.com: unattended-upgrades doesn't seem to have a 'fancy' LSB output in the init.d Could you please add them? I've updated u-a script to be fancy! :-) Hopefully I haven't introduced any functional changes. I've used the example from skeleton script.

Bug#647476: unattended-upgrades: should not call dpkg unless doing some pkgs upgrades

2012/6/13 Michael Vogt m...@debian.org: b) not do that at all and provide a different (hidden) option to   enable this behavior as only useful in rare debugging cases This seems more appropriate to me, probably enabled by --debug. Thanks -- To UNSUBSCRIBE, email to

Bug#647476: unattended-upgrades: should not call dpkg unless doing some pkgs upgrades

2012/6/12 Michael Vogt m...@debian.org: On Thu, Nov 24, 2011 at 02:48:58PM +0200, Teodor MICU wrote: I've found a corner case were u-a still executes 'dpkg' when invoked with --dry-run. There are packages that should be upgraded but no upgrade is performed because it was instructed by '--dry

Bug#673185: gnome-shell: segfault in libaccountsservice.so.0.0.0

By following the gdb example below I've obtained a (different) backtrace by unplugging the power cord from laptop. This is the voluntary trigger of this bug for me. BTW, this is now a problem for those that use systemd as well. Up to version 0.6.21-1, when using systemd init, gnome-shell did not

Bug#673185: gnome-shell: segfault in libaccountsservice.so.0.0.0

Attaching the file ... 2012/6/10 Teodor MICU mteo...@gmail.com: By following the gdb example below I've obtained a (different) backtrace by unplugging the power cord from laptop. This is the voluntary trigger of this bug for me. Starting program: /usr/bin/gnome-shell --replace --display :0

Bug#674755: systemd: tmpfs inconsistencies (/run/lock, /run/shm, /tmp)

Why close the bug without at least a response?! 2012/6/5 Tollef Fog Heen tfh...@err.no: ]] Teodor The default Debian init mounts several tmpfs as indicated by the config - /run/shm But with init=/bin/systemd I see these mount entries: - /dev/shm I'm not sure what you think the bug is

Bug#670097: gnome-shell: random hang causes data loss

I'm still getting these gnome-shell freezes. I've attached a bt full from the latest one (it appears to have all the debug info). Note, this is different then the 'accountsservice' problem were gnome-shell will respawn or crash. As usual, the only know workaround is to 'pkill -2 gnome-session'.

Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0

Although it appeared that the problem is fixed in version 0.6.21-2, after several hours the problem reoccurred. Indeed, the crash is not that frequent and most important I didn't had a full gnome-shell crash (it restarted automatically). I can still reproduce the problem by just unplugging the

Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0

Apparently, using systemd avoids the crash in gnome-shell. This seems to be a good guess of Michael Biebl in bug#674433, so both problems appear to have the same root. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#670097: gnome-shell: random hang causes data loss

severity 670097 important stop I had no other occurrence of this problem for 2-3 weeks. Because there is a workaround (kill gnome-shell) I downgraded the bug severity. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0

severity 673185 grave stop This problem affects gnome-shell even more. If I'm on battery the gnome-shell process is killed but not restarted afterwards. The only way to obtain a somehow stable X/gnome session was to restart gdm3. I still get the gnome-shell respawn but I least I'm not forced into

Bug#673185: Fwd: Bug#673185: gnome-shell: segfault error 4 in libaccountsservice.so.0.0.0

I just read [1] that this problem is caused by «cogl», should I reassign? I've had another occurrence one hour ago (log entries attached). These are all «ocgl» related packages currently installed: ii  gir1.2-cogl-1.0      1.10.2-3 ii  gir1.2-coglpango-1.0 1.10.2-3 ii  libcogl-pango0:amd64

Bug#672160: Directory /boot/console-setup

2012/5/12 Steve Langasek vor...@debian.org: There is no way to tell whether a file in /etc/console-setup is owned by the package console-setup or it has been put there by the admin and is unrelated to console-setup. Who cares? And most package maintainers have not bothered to implement such

Bug#671474: roundcube: main.inc.php must have group set to 'www-data'

2012/5/4 Vincent Bernat ber...@debian.org: I have little control  on main.inc.php.ucf-dist. I apply the appropriate rights for main.inc.php in postinst but  I don't see any way to tell ucf what should be the owner  of main.inc.ucf-dist. Therefore, I have no fix to propose. Ok, only

Bug#670097: gnome-shell: random hang causes data loss

2012/4/30 Michael Biebl bi...@debian.org: From time to time the Gnome shell will just freeze/hang and not accept any input How often is from time to time? Is this related to specific actions/circumstances, e.g. running an OpenGL game or something similar. At least once a week. Usually I run

Bug#625847: unattended-upgrades: should not send an email if no package was upgraded

2012/4/26 Michael Vogt m...@debian.org: This bugreport is interessting and I'm happy to implement the required change to not send a mail if nothing changes. However I wonder if that is what should be default? Great. I mean, it seems like its very interessting to know that a package did

Bug#670131: AttributeError: 'Version' object has no attribute 'policy_priority'

2012/4/24 Michael Vogt m...@debian.org: This should work with current sid but it will not work with older version of python-apt. I added a check into do the code to not crash if it runs with older versions of python-apt. Thanks. I realised after sending the report that severity grave was not

Bug#625847: unattended-upgrades: should not send an email if no package was upgraded

I've retested this problem with u-a version 0.76.3 and I see that the problem is still not fixed but also that the logic is already implemented in another block: saving a log file or not. See attached debug log. That message was printed only on console (stdout), even though the last lines are

Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012/4/23 Jonathan Nieder jrnie...@gmail.com: Great, thanks for testing.  How about the second question --- is the radeon firmware installed?  You can find out with        dpkg -l firmware-linux Just to be clear, if the bug is only reproducible when the radeon firmware is not installed, it

Bug#586995: KMS not working on ATI Technologies Inc M56P [Radeon Mobility X1600]

2012/4/18 Jonathan Nieder jrnie...@gmail.com: Thanks for a reminder.  If you install a current squeeze kernel (e.g., 2.6.32-43) on the wheezy system, does it still reproduce modesetting trouble?  Is the radeon firmware installed? I just tested this (linux image from stable-proposed-updates)

Bug#669583: OSError: [Errno 1] Operation not permitted

2012/4/20 Michael Vogt m...@debian.org: Thanks for your bugreport. I fixed that now. I guess in your case it was already the session-leader for some reason (maybe because of systemd?). Yes, I use «systemd» but I don't know what being session-leader means. Most times u-a is run automatically by

Bug#669583: OSError: [Errno 1] Operation not permitted

2012/4/20 Michael Vogt m...@debian.org: Sure, the setsid() call makes the process a session leader and removes the controlling tty. The rational is that if you run unattended-upgrades in a shell and then shutdown your tty goes away and unattended-upgrades gets killed even if its in the middle

Bug#665705: Doesn't upgrade upgradable packages when others are not upgradable

I cannot reproduce this problem, even more I see the opposite on one of my hosts: | Packages that are upgraded: | apache2-utils | Packages with upgradable origin but kept back: | apache2.2-common apache2 apache2-mpm-prefork apache2.2-bin Could you please run on that machine (as root): #

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

Ping? I would like to have this fixed in wheezy so that I don't have to keep installing u-a from sid (as I do for current stable - squeeze). I keep getting a daily email due to the latest 'apache2' security fixes. Probably most corporations have a local policy in place to not upgrade the packages

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

2012/4/19 Michael Vogt m...@debian.org: Right, so I added the print there on purpose to ensure that users are informed that there is a package held back. It maybe the wrong tradeoff, in the current version I added code that will only print if there is no summary mail. That may still not be

Bug#669583: OSError: [Errno 1] Operation not permitted

One important detail: I use «systemd», so this might not be a bug in U-A. Thaks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#661217: systemd: gdm3 does not start

Version: 44-1 The problem is fixed in the latest version, I can run systemd on both my homestation and my laptop. The above line should close the bug or an email to #-done@b.d.o is necessary. 2012/2/26 Michael Biebl bi...@debian.org: Most likely a duplicate of

Bug#666523: libreoffice: upgrade to 1:3.5.2~rc2-1 utterly fails

2012/4/2 Rene Engelhard r...@debian.org: On Mon, Apr 02, 2012 at 07:06:26PM +0300, Teodor MICU wrote: I've had this problem on my homestation. I fixed it by setting LANG=C and run the upgrade again. [..] I *think* that this is just by chance. I also get a error with just C the first time

Bug#666523: libreoffice: upgrade to 1:3.5.2~rc2-1 utterly fails

I've had this problem on my homestation. I fixed it by setting LANG=C and run the upgrade again. On this host I don't have en_US at all but only ro_RO.UTF-8. Hope this helps as this seemed to be a locale problem. Thanks -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

  1   2   3   >