Bug#1070251: tt-rss: LibXML error 4 at line 1 (column 1): Start tag expected, '<' not found
Package: tt-rss Version: 21~git20210204.b4cbc79+dfsg-1.2 Severity: important Dear Maintainer, At the moment I have a few RSS-feeds that have an error and more feeds are getting the same error. "LibXML error 4 at line 1 (column 1): Start tag expected, '<' not found" This is shown at least for the following feeds: https://gohugo.io/news/index.xml http://www.blender.org/feed/ https://blog.gitea.io/index.xml When I look at the feeds themselves, I do not see an issue with them, so I would expect that tt-rss would be able to handle them. It might have to do with a libxml2 package update I did recently. 2024-05-01 22:22:55 upgrade libxml2:amd64 2.9.14+dfsg-1.3+b2 2.9.14+dfsg-1.3+b3 I already restarted tt-rss, but this does not solve the issue. -- System Information: Debian Release: trixie/sid APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages tt-rss depends on: ii dbconfig-common 2.0.24 ii dbconfig-mysql2.0.24 ii debconf [debconf-2.0] 1.5.86 ii fonts-material-design-icons-iconfont 6.7.0+dfsg-1 ii init-system-helpers 1.66 ii libapache2-mod-php8.2 [php-json] 8.2.12-1+b1 ii libjs-dojo-core 1.17.2+dfsg1-2.1 ii libjs-dojo-dijit 1.17.2+dfsg1-2.1 ii libjs-scriptaculous 1.9.0-3 ii lsb-base 11.6 ii php 2:8.2+93 ii php-cli 2:8.2+93 ii php-intl 2:8.2+93 ii php-json 2:8.2+93 ii php-mbstring 2:8.2+93 ii php-mysql 2:8.2+93 ii php-pgsql 2:8.2+93 ii php-php-gettext 1.0.12-6 ii php-psr-log 1.1.4-2 ii php-xml 2:8.2+93 ii php8.2 [php] 8.2.12-1 ii php8.2-cli [php-json] 8.2.12-1+b1 ii php8.2-fpm [php-json] 8.2.12-1+b1 ii php8.2-intl [php-intl]8.2.12-1+b1 ii php8.2-mbstring [php-mbstring]8.2.12-1+b1 ii php8.2-pgsql [php-pgsql] 8.2.12-1+b1 ii php8.2-phpdbg [php-json] 8.2.12-1+b1 ii php8.2-xml [php-xml] 8.2.12-1+b1 ii phpqrcode 1.1.4-3.1 ii sysvinit-utils [lsb-base] 3.09-1 Versions of packages tt-rss recommends: ii apache2 [httpd] 2.4.58-1+b1 ii ca-certificates 20240203 ii nginx [httpd] 1.24.0-2+b1 ii php-curl2:8.2+93 ii php-gd 2:8.2+93 pn php-mcrypt ii php8.2-curl [php-curl] 8.2.12-1+b1 ii php8.2-gd [php-gd] 8.2.12-1+b1 Versions of packages tt-rss suggests: pn php-apc pn sphinxsearch -- Configuration Files: /etc/tt-rss/config.php changed [not included] -- debconf information: tt-rss/passwords-do-not-match: * tt-rss/database-type: pgsql tt-rss/mysql/method: Unix socket tt-rss/pgsql/authmethod-admin: ident tt-rss/install-error: abort tt-rss/mysql/admin-user: tt-rss/dbconfig-reinstall: false tt-rss/pgsql/manualconf: tt-rss/internal/skip-preseed: false tt-rss/dbconfig-remove: true * tt-rss/self_url_path: http://localhost/ tt-rss/db/basepath: tt-rss/mysql/authplugin: default tt-rss/missing-db-package-error: abort * tt-rss/dbconfig-install: true tt-rss/internal/reconfiguring: false tt-rss/remove-error: abort * tt-rss/reconfigure-webserver: tt-rss/pgsql/changeconf: false tt-rss/dbconfig-upgrade: true * tt-rss/remote/host: localhost tt-rss/pgsql/method: TCP/IP tt-rss/db/app-user: ttrss@localhost tt-rss/purge: false tt-rss/upgrade-backup: true tt-rss/db/dbname: ttrss tt-rss/upgrade-error: abort tt-rss/remote/port: tt-rss/pgsql/no-empty-passwords: tt-rss/pgsql/admin-user: postgres tt-rss/pgsql/authmethod-user: password tt-rss/remote/newhost: localhost
Bug#1053348: atop gets a segmentation fault
On Sat, Jan 13, 2024 at 09:55:46PM +0100, Marc Haber wrote: > On Mon, Oct 02, 2023 at 12:50:04PM +0200, Tiger!P wrote: > > I ran `atop 2` for some time and then it got a segmentation fault. > > Because it didn't create a core file, I changed settings to get a > > core file and started atop in the same way. > > Does this still happen with the new atop version in sid? I have not seen a segfault with 2.10.0-1 yet. I have updated atop to 2.10.0-1 on multiple system and will report when I see a crash again. Tiger!P
Bug#1031174: transmission-gtk: Transmission 4.0.0 is available
Package: transmission-gtk Version: 3.00-2.1+b1 Severity: normal Dear Maintainer, Transmission 4.0.0 has been released [1]. Could you create a package for this new version? [1] https://transmissionbt.com/download and https://github.com/transmission/transmission/releases/tag/4.0.0 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-6-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages transmission-gtk depends on: ii libayatana-appindicator3-1 0.5.92-1 ii libc6 2.36-8 ii libcurl47.87.0-2 ii libevent-2.1-7 2.1.12-stable-5+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libglib2.0-02.74.5-1 ii libgtk-3-0 3.24.36-3 ii libminiupnpc17 2.2.4-1+b1 ii libnatpmp1 20150609-7.1+b2 ii libpango-1.0-0 1.50.12+ds-1 ii libssl3 3.0.7-2 ii transmission-common 3.00-2.1 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages transmission-gtk recommends: ii xdg-utils 1.1.3-4.1 transmission-gtk suggests no packages. -- no debconf information
Bug#1029197: ip-transparent: yes is blocked by apparmor
Package: unbound Version: 1.17.0-1 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? I wanted to configure a static IPv6 address in unbound, but that is not (always) available when booting the system. Therefor I enabled ip-transparent in the server section. * What exactly did you do (or not do) that was effective (or ineffective)? When I enabled 'ip-transparent: yes' in the server section, apparmor blocked some capabilities when restarting unbound. Jan 19 13:37:20 kernel: audit: type=1400 audit(1674131840.250:65): apparmor="DENIED" operation="capable" profile="unbound" pid=1072585 comm="unbound" capability=13 capname="net_raw" Jan 19 13:37:20 kernel: audit: type=1400 audit(1674131840.250:66): apparmor="DENIED" operation="capable" profile="unbound" pid=1072585 comm="unbound" capability=12 capname="net_admin" * What outcome did you expect instead? I would have expected that unbound would not be blocked by apparmor and would be able to use the ip-transparent option without issue. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unbound depends on: ii adduser3.130 ii init-system-helpers1.65.2 ii libc6 2.36-8 ii libevent-2.1-7 2.1.12-stable-5+b1 ii libnghttp2-14 1.51.0-1 ii libprotobuf-c1 1.4.1-1+b1 ii libpython3.10 3.10.9-1 ii libssl33.0.7-1 ii libsystemd0252.4-1 ii lsb-base 11.5 ii sysvinit-utils [lsb-base] 3.06-2 Versions of packages unbound recommends: ii dns-root-data 2023010101 Versions of packages unbound suggests: ii apparmor 3.0.8-1 ii openssl 3.0.7-1 -- no debconf information Content-Type: multipart/mixed; boundary="===4881449298252092416==" MIME-Version: 1.0 From: TigerP To: Debian Bug Tracking System Subject: ip-transparent: yes is blocked by apparmor Bcc: TigerP Message-ID: <167413411988.1072823.1845641849211757387.report...@melaine.andor.aybara.org> X-Mailer: reportbug 11.6.0 Date: Thu, 19 Jan 2023 14:15:19 +0100 This is a multi-part MIME message sent by reportbug. --===4881449298252092416== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Package: unbound Version: 1.17.0-1 Severity: normal Tags: patch Dear Maintainer, * What led up to the situation? I wanted to configure a static IPv6 address in unbound, but that is not (always) available when booting the system. Therefor I enabled ip-transparent in the server section. * What exactly did you do (or not do) that was effective (or ineffective)? When I enabled 'ip-transparent: yes' in the server section, apparmor blocked some capabilities when restarting unbound. Jan 19 13:37:20 kernel: audit: type=1400 audit(1674131840.250:65): apparmor="DENIED" operation="capable" profile="unbound" pid=1072585 comm="unbound" capability=13 capname="net_raw" Jan 19 13:37:20 kernel: audit: type=1400 audit(1674131840.250:66): apparmor="DENIED" operation="capable" profile="unbound" pid=1072585 comm="unbound" capability=12 capname="net_admin" * What outcome did you expect instead? I would have expected that unbound would not be blocked by apparmor and would be able to use the ip-transparent option without issue. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unbound depends on: ii adduser3.130 ii init-system-helpers1.65.2 ii libc6 2.36-8 ii libevent-2.1-7 2.1.12-stable-5+b1 ii libnghttp2-14 1.51.0-1 ii libprotobuf-c1 1.4.1-1+b1 ii libpython3.10 3.10.9-1 ii libssl33.0.7-1 ii libsystemd0252.4-1 ii lsb-base 11.5 ii sysvinit-utils [lsb-base] 3.06-2 Versions of packages unbound recommends: ii dns-root-data 2023010101 Versions of packages unbound suggests: ii apparmor 3.0.8-1 ii openssl 3.0.7-1 -- no debconf information --===4881449298252092416== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0
Bug#935625: preseed: lvm commands during preseed/late_command don't finish
On Sun, Aug 25, 2019 at 08:26:26AM +0200, Cyril Brulebois wrote: > Hi, Hello Cyril, > Tiger!P (2019-08-24): > > When using a preseed file to install a system, it is not possible to > > keep a part of the VG free for future use. > > I'm not sure this is true: > > https://salsa.debian.org/installer-team/installation-guide/commit/07d72d9a8afc201949ee116506564645e91d618f I was not aware of this option, because it is not yet available in the preseed file which is mentioned in appendix B.4 of the stable release notes. Thank you for pointing it out. I tested the option and it works as expected :-) Even though the lvm commands still hang, you can close this bug if you want to. Tiger!P
Bug#935625: preseed: lvm commands during preseed/late_command don't finish
zed:0 locked:0 critical:0 daemon:0 suspended:0 #format_text/archiver.c:571 Creating volume group backup "/etc/lvm/backup/sulin" (seqno 6). #format_text/format-text.c:1323 Writing sulin metadata to /etc/lvm/backup/.lvm_sulin-test_26292_13185384 #format_text/format-text.c:1342 Renaming /etc/lvm/backup/.lvm_sulin-test_26292_13185384 to /etc/lvm/backup/sulin.tmp #format_text/format-text.c:1367 Committing file sulin metadata (6) #format_text/format-text.c:1368 Renaming /etc/lvm/backup/sulin.tmp to /etc/lvm/backup/sulin #metadata/lv_manip.c:6305Logical volume "keep_2" successfully removed #mm/memlock.c:594 Unlock: Memlock counters: prioritized:0 locked:0 critical:0 daemon:0 suspended:0 #activate/fs.c:491 Syncing device names #device_mapper/libdm-common.c:2362 Udev cookie 0xd4db7eb (semid 0) decremented to 1 #device_mapper/libdm-common.c:2648 Udev cookie 0xd4db7eb (semid 0) waiting for zero ^C # lvs LV VGAttr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home sulin -wi-ao 6.98g root sulin -wi-ao <9.54g swap_1 sulin -wi-ao 976.00m # If you have any questions, please ask. Tiger!P
Bug#935043: deluge-gtk: Unable to use Move Storage in context menu, it gives a TypeError
Package: deluge-gtk Version: 1.3.15-2 Severity: important Dear Maintainer, * What led up to the situation? I started deluge-gtk in a xterm and connected it to a deluged process on the local machine. I used the context menu on a torrent to try to move the torrent's files to a different location * What exactly did you do (or not do) that was effective (or ineffective)? I used the context menu and clicked on Move Storage and expected a file dialog to appear in which I could select the new destination directory. * What was the outcome of this action? Nothing appeared or was done. On the console I saw the following message: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/deluge/ui/gtkui/menubar.py", line 328, in on_menuitem_move_activate chooser.set_current_folder(config["choose_directory_dialog_path"]) TypeError: Gtk.FileChooser.set_current_folder() argument 1 must be string, not None * What outcome did you expect instead? As mentioned above, I expected a file dialog to appear. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-4-amd64 (SMP w/2 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages deluge-gtk depends on: ii deluge-common 1.3.15-2 ii gnome-flashback [notification-daemon] 3.30.0-3 ii librsvg2-common2.44.14-1 ii notification-daemon3.20.0-4 ii python 2.7.16-1 ii python-glade2 2.24.0-6 ii python-notify 0.1.1-4+b2 ii xdg-utils 1.1.3-1 Versions of packages deluge-gtk recommends: ii python-pygame 1.9.4.post1+dfsg-3 deluge-gtk suggests no packages. -- no debconf information
Bug#932484: isso gives 404 when started via systemd
Package: isso Version: 0.12.2-2 Severity: important Dear Maintainer, * What led up to the situation? I tried to use isso by starting is via systemd. * What exactly did you do (or not do) that was effective (or ineffective)? I started isso via systemd (systemctl start isso) which then listens on 127.0.0.1:8000 and then I tried to get the /js/embed.min.js from that process by using wget. * What was the outcome of this action? The wget resulted in a http 404. * What outcome did you expect instead? I would expect to get the embed.min.js from isso. When I start isso manually (su -s /bin/bash -l isso -c "isso -c /etc/isso.d/enabled/example.cfg") it listens on 127.0.0.1:8080 and when I do a wget to get /js/embed.min.js from that process it works. Please let me know if you need more information. -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages isso depends on: ii lsb-base 10.2019051400 ii python3 3.7.3-1 ii python3-bleach3.1.0-1 ii python3-html5lib 1.0.1-1 ii python3-itsdangerous 0.24+dfsg1-2 ii python3-jinja22.10.1-1 ii python3-misaka1.0.2-5+b3 ii python3-werkzeug 0.14.1+dfsg1-4 Versions of packages isso recommends: ii gunicorn3 19.9.0-1 ii libjs-jquery 3.3.1~dfsg-3 ii libjs-underscore 1.9.1~dfsg-1 isso suggests no packages. -- no debconf information
Bug#911107: Acknowledgement (deluged sends port=0 via IPv6 announce instead of the correct port)
Hello, This bug has been fixed in the new upstream release 1.1.11 [1]. [1] https://github.com/arvidn/libtorrent/releases/tag/libtorrent_1_1_11 -- Tiger!P
Bug#911107: Acknowledgement (deluged sends port=0 via IPv6 announce instead of the correct port)
Hello,
This issue has also been reported to upstream as #3306 [1] and has been
fixed with PR #3385 [2]. And it will be available in the next 1.1.X
release.
I've added the patch that can be applied to fix the issue.
[1] https://github.com/arvidn/libtorrent/issues/3306
[2] https://github.com/arvidn/libtorrent/pull/3385
--
Tiger!P
Index: libtorrent-rasterbar-1.1.9/src/session_impl.cpp
===
--- libtorrent-rasterbar-1.1.9.orig/src/session_impl.cpp2018-07-29
21:56:52.0 +0200
+++ libtorrent-rasterbar-1.1.9/src/session_impl.cpp 2018-10-28
19:41:59.391255210 +0100
@@ -1320,7 +1320,7 @@
#ifdef TORRENT_USE_OPENSSL
// SSL torrents use the SSL listen port
if (req.ssl_ctx) req.listen_port = ssl_listen_port();
- req.ssl_ctx = _ssl_ctx;
+ else req.ssl_ctx = _ssl_ctx;
#endif
#if TORRENT_USE_I2P
if (!m_settings.get_str(settings_pack::i2p_hostname).empty())
@@ -1334,6 +1334,24 @@
{
req.bind_ip = m_listen_interface.address();
}
+
+#ifndef TORRENT_DISABLE_LOGGING
+ session_log("==> TRACKER REQUEST \"%s\" event: %s abort: %d
ssl: %p "
+ "port: %d force-proxy: %d bind_ip: %s"
+ , req.url.c_str()
+ , (req.event==tracker_request::stopped?"stopped"
+ : req.event==tracker_request::started?"started":"-")
+ , m_abort
+#ifdef TORRENT_USE_OPENSSL
+ , static_cast(req.ssl_ctx)
+#else
+ , static_cast(0)
+#endif
+ , req.listen_port
+ , m_settings.get_bool(settings_pack::force_proxy)
+ , req.bind_ip ? req.bind_ip->to_string().c_str() : ""
+ );
+#endif
m_tracker_manager.queue_request(get_io_service(), req, c);
}
@@ -5510,7 +5528,16 @@
// potentially identify us if it is leaked elsewere
if (m_settings.get_bool(settings_pack::force_proxy)) return 0;
if (m_listen_sockets.empty()) return 0;
+#ifdef TORRENT_USE_OPENSSL
+ for (std::list::const_iterator i =
m_listen_sockets.begin()
+ , end(m_listen_sockets.end()); i != end; ++i)
+ {
+ if (!i->ssl) return i->external_port;
+ }
+ return 0;
+#else
return m_listen_sockets.front().external_port;
+#endif
}
boost::uint16_t session_impl::ssl_listen_port() const
Index: libtorrent-rasterbar-1.1.9/src/torrent.cpp
===
--- libtorrent-rasterbar-1.1.9.orig/src/torrent.cpp 2018-07-29
21:56:52.0 +0200
+++ libtorrent-rasterbar-1.1.9/src/torrent.cpp 2018-10-28 19:46:40.731038658
+0100
@@ -3374,12 +3374,6 @@
#endif
#ifndef TORRENT_DISABLE_LOGGING
- debug_log("==> TRACKER REQUEST \"%s\" event: %s abort:
%d"
- , req.url.c_str()
- , (req.event==tracker_request::stopped?"stopped"
-
:req.event==tracker_request::started?"started":"")
- , m_abort);
-
// if we're not logging session logs, don't bother
creating an
// observer object just for logging
if (m_abort && alerts().should_post())
@@ -3713,6 +3707,9 @@
req.private_torrent = m_torrent_file->priv();
req.second_announce = true;
+#ifdef TORRENT_USE_OPENSSL
+ req.ssl_ctx = NULL;
+#endif
// tell the tracker to bind to the opposite
protocol type
req.bind_ip = tracker_ip.is_v4()
Index: libtorrent-rasterbar-1.1.9/src/tracker_manager.cpp
===
--- libtorrent-rasterbar-1.1.9.orig/src/tracker_manager.cpp 2018-07-29
21:56:49.0 +0200
+++ libtorrent-rasterbar-1.1.9/src/tracker_manager.cpp 2018-10-28
19:48:48.078940858 +0100
@@ -288,11 +288,7 @@
, req.listen_port);
#endif
- TORRENT_ASSERT(!m_abort || req.event ==
tracker_request::stopped);
- if (m_abort && req.event != tracker_request::stopped)
- return;
-
- std::string protocol = req.url.substr(0, req.url.find(':'));
+ std::string const protocol = req.url.substr(0,
req.url.find(':'));
#ifdef TORRENT_USE_OPENSSL
if (protocol == "http" || protocol == "https")
Bug#911107: deluged sends port=0 via IPv6 announce instead of the correct port
Originally I reported this on the deluged package, but I think it is in libtorrent. I think this has also been reported [1] to the upstream of libtorrent [1] https://github.com/arvidn/libtorrent/issues/3306 Tiger!P
Bug#911107: deluged sends port=0 via IPv6 announce instead of the correct port
Package: deluged Version: 1.3.15-2 Severity: important Tags: ipv6 Dear Maintainer, * What led up to the situation? My system has both IPv4 and IPv6 connections and I used deluged to get the debian-9.5.0-amd64-netinst.iso . * What exactly did you do (or not do) that was effective (or ineffective)? When I did an update tracker, I saw that 2 announce messages are sent. One to the tracker's IPv4 address and one to the tracker's IPv6 address, but the last one sent port=0 instead of the correct portnumber. * What was the outcome of this action? I did a tcpdump of the connection to the debian tracker and saw the following data: To 130.239.18.159 on port 6969: ..`.NGD.GET /announce?info_hash=%3b%1d%85%f8x%0e%f8%c4%d8S%8f%80%9azc%fcR%991%8e_id=-DE13F0-a7HtrDr99EyW=28741=0=0=0=0=EBA0497F=started=200=1_peer_id=1=1=0 HTTP/1.1 Host: bttracker.debian.org:6969 User-Agent: Deluge 1.3.15 Accept-Encoding: gzip Connection: close and to 2001:6b0:e:2018::159 on port 6969: ..5ENGD.GET /announce?info_hash=%3b%1d%85%f8x%0e%f8%c4%d8S%8f%80%9azc%fcR%991%8e_id=-DE13F0-a7HtrDr99EyW=0=0=0=0=0=EBA0497F=started=200=1_peer_id=1=1=0 HTTP/1.1 Host: bttracker.debian.org:6969 User-Agent: Deluge 1.3.15 Accept-Encoding: gzip Connection: close Here you can see the port=0 part of the announce message, which will make the tracker think the client is listening on port 0, but it is not. * What outcome did you expect instead? I would expect that both the IPv4 and IPv6 announce messages would send the correct port * Additional information: I used deluge-gtk to talk to the deluged daemon. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages deluged depends on: ii adduser3.118 ii deluge-common 1.3.15-2 ii lsb-base 9.20170808 ii python 2.7.15-3 ii python-libtorrent 1.1.9-1 deluged recommends no packages. deluged suggests no packages. -- no debconf information
Bug#877715: apache2: apache won't start after reboot when listening on IPv6 address
On Sun, Oct 08, 2017 at 04:48:49PM +0200, Stefan Fritsch wrote: > On Wednesday, 4 October 2017 20:41:38 CEST Tiger!P wrote: > > I tried to add a file /etc/systemd/system/apache2.service.d/after.conf > > with the following content: > > 8< > > [Unit] > > Wants=network-online.target > > After=network.target remote-fs.target nss-lookup.target > > network-online.target > > 8< > > Can you check if > > systemctl enable ifupdown-wait-online.service root@debian9:~# systemctl enable ifupdown-wait-online.service Failed to enable unit: File ifupdown-wait-online.service: No such file or directory root@debian9:~# > helps? If not, what is the output of > > systemctl status ifupdown-wait-online.service root@debian9:~# systemctl status ifupdown-wait-online.service Unit ifupdown-wait-online.service could not be found. root@debian9:~# Which packages provides ifupdown-wait-online.service ? Because I can't find it for stretch when searching on packages.debian.org [1]. I did find it for sid [2], but I think it is not available for stretch. Do I need to test the bug with sid or add the ifupdown-wait-online.service to stretch and see if it helps? [1] https://packages.debian.org/search?searchon=contents=ifupdown-wait-online.service=path=stable=any [2] https://packages.debian.org/search?suite=sid=any=path=contents=ifupdown-wait-online.service Tiger!P
Bug#877715: apache2: apache won't start after reboot when listening on IPv6 address
Package: apache2 Version: 2.4.25-3+deb9u3 Severity: normal Dear Maintainer, * What led up to the situation? I wanted to let apache listen on a specific IPv6 address and this works when the system is running, but it doesn't work when the system is (re)booted. * What exactly did you do (or not do) that was effective (or ineffective)? I tried to add a file /etc/systemd/system/apache2.service.d/after.conf with the following content: 8< [Unit] Wants=network-online.target After=network.target remote-fs.target nss-lookup.target network-online.target 8< But this didn't help to get apache running when the system boots. * What was the outcome of this action? There was no change when booting the system, apache still failed with the following log: Oct 01 22:41:17 debian9 systemd[1]: Starting The Apache HTTP Server... Oct 01 22:41:17 debian9 apachectl[384]: (99)Cannot assign requested address: AH00072: make_sock: could not bind to address [2001:888:148c::1:1]:443 Oct 01 22:41:17 debian9 apachectl[384]: no listening sockets available, shutting down Oct 01 22:41:17 debian9 apachectl[384]: AH00015: Unable to open logs Oct 01 22:41:17 debian9 apachectl[384]: Action 'start' failed. Oct 01 22:41:17 debian9 apachectl[384]: The Apache error log may have more information. Oct 01 22:41:17 debian9 systemd[1]: apache2.service: Control process exited, code=exited status=1 Oct 01 22:41:17 debian9 systemd[1]: Failed to start The Apache HTTP Server. Oct 01 22:41:17 debian9 systemd[1]: apache2.service: Unit entered failed state. Oct 01 22:41:17 debian9 systemd[1]: apache2.service: Failed with result 'exit-code'. * What outcome did you expect instead? I would expect apache to start when the system boots. -- Package-specific info: -- System Information: Debian Release: 9.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apache2 depends on: ii apache2-bin 2.4.25-3+deb9u3 ii apache2-data 2.4.25-3+deb9u3 ii apache2-utils2.4.25-3+deb9u3 ii dpkg 1.18.24 ii init-system-helpers 1.48 ii lsb-base 9.20161125 ii mime-support 3.60 ii perl 5.24.1-3+deb9u2 ii procps 2:3.3.12-3 Versions of packages apache2 recommends: ii ssl-cert 1.0.39 Versions of packages apache2 suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom pn www-browser Versions of packages apache2-bin depends on: ii libapr1 1.5.2-5 ii libaprutil1 1.5.4-3 ii libaprutil1-dbd-sqlite3 1.5.4-3 ii libaprutil1-ldap 1.5.4-3 ii libc62.24-11+deb9u1 ii libldap-2.4-22.4.44+dfsg-5 ii liblua5.2-0 5.2.4-1.1+b2 ii libnghttp2-141.18.1-1 ii libpcre3 2:8.39-3 ii libssl1.0.2 1.0.2l-2 ii libxml2 2.9.4+dfsg1-2.2+deb9u1 ii perl 5.24.1-3+deb9u2 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages apache2-bin suggests: pn apache2-doc pn apache2-suexec-pristine | apache2-suexec-custom pn www-browser Versions of packages apache2 is related to: ii apache2 2.4.25-3+deb9u3 ii apache2-bin 2.4.25-3+deb9u3 -- Configuration Files: /etc/apache2/ports.conf changed: Listen 80 #Listen 443 Listen 127.0.0.1:443 Listen [2001:888:148c::1:1]:443 Listen 443 part of /etc/network/interfaces: iface enp0s3 inet6 static address 2001:888:148c::1:1 netmask 64 gateway fe80::f29f:c2ff:fe10:469e -- no debconf information
Bug#869364: libtext-iconv-perl: unable to install libtext-iconv-perl (1.7-5) on Debian sid
Package: libtext-iconv-perl Version: 1.7-5 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? Trying to install the package * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? # apt-get install libtext-iconv-perl Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libtext-iconv-perl : Depends: perlapi-5.24.1 E: Unable to correct problems, you have held broken packages. # dpkg -l perl-base Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii perl-base 5.26.0-4 amd64minimal Perl system # * What outcome did you expect instead? I would expect the package to be installed. It seems the package still depends on perl-base 5.24.1 when perl-5.26.0 is installed by all updates. -- System Information: Debian Release: buster/sid APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.5.7-std-3 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libtext-iconv-perl depends on: ii libc6 2.24-12 ii perl-base 5.26.0-4 pn perlapi-5.24.1 libtext-iconv-perl recommends no packages. libtext-iconv-perl suggests no packages.
Bug#851268: sopel: first sopel start fails because of missing configration
Package: sopel
Version: 6.5.0-1
Severity: important
Dear Maintainer,
Thank you for creating the sopel package for Debian.
* What led up to the situation?
I installed the package and tried to configure it by using the commands
which were in the README.Debian file.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I ran the following commands as root:
chown sopel /etc/sopel.cfg
sudo -u sopel sopel --config /etc/sopel.cfg --configure-all
* What was the outcome of this action?
Creating a config directory at ~/.sopel...
Please answer the following questions to create your configuration file:
Encountered an error while writing the config file. This shouldn't happen.
Check permissions.
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sopel/config/types.py", line 338, in
parse
os.makedirs(value)
File "/usr/lib/python3.5/os.py", line 241, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/etc/logs'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sopel/config/types.py", line 59, in
__init__
getattr(self, value)
File "/usr/lib/python3/dist-packages/sopel/config/types.py", line 306, in
__get__
return self.parse(main_config, this_section, value)
File "/usr/lib/python3/dist-packages/sopel/config/types.py", line 341, in
parse
"Value must be an existing or creatable directory.")
ValueError: Value must be an existing or creatable directory.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/sopel", line 11, in
load_entry_point('sopel==6.5.0', 'console_scripts', 'sopel')()
File "/usr/lib/python3/dist-packages/sopel/run_script.py", line 111, in main
_wizard('all', opts.config)
File "/usr/lib/python3/dist-packages/sopel/config/__init__.py", line 217, in
_wizard
_create_config(configpath)
File "/usr/lib/python3/dist-packages/sopel/config/__init__.py", line 250, in
_create_config
config = Config(configpath, validate=False)
File "/usr/lib/python3/dist-packages/sopel/config/__init__.py", line 64, in
__init__
validate=validate)
File "/usr/lib/python3/dist-packages/sopel/config/__init__.py", line 118, in
define_section
setattr(self, name, cls_(self, name, validate=validate))
File "/usr/lib/python3/dist-packages/sopel/config/types.py", line 63, in
__init__
str(e))
ValueError: Invalid value for core.logdir: Value must be an existing or
creatable directory.
* What outcome did you expect instead?
The possibility to configure sopel.
To be able to configure sopel, the command should be:
sudo -u sopel sopel --config /etc/sopel --configure-all
Notice there is no .cfg at the end of the config file.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sopel depends on:
ii adduser 3.115
ii init-system-helpers 1.46
ii lsb-base 9.20161125
ii python3-enchant 1.6.7-1
ii python3-requests 2.12.4-1
ii python3-tz 2016.7-0.2
pn python3:any
Versions of packages sopel recommends:
ii ipython35.1.0-3
ii python3-feedparser 5.1.3-3
ii python3-lxml3.6.4-1
ii python3-praw3.3.0-1
ii python3-xmltodict 0.10.2-1
sopel suggests no packages.
-- Configuration Files:
/etc/sopel.cfg changed [not included]
-- no debconf information
Bug#818372: Problem when updating testing
On Fri, May 06, 2016 at 07:34:03PM +0900, Norbert Preining wrote: > > I have a similar issue with tex-common > > This is a different issue. > > Please *read* the error mesages: > > > updmap [ERROR]: epiolmec.map (in > > /usr/local/share/texmf/web2c/updmap.cfg) > > updmap [ERROR]: esint.map (in > > /usr/local/share/texmf/web2c/updmap.cfg) > > updmap [ERROR]: stmaryrd.map (in > > /usr/local/share/texmf/web2c/updmap.cfg) > > updmap [ERROR]: xypic.map (in > > /usr/local/share/texmf/web2c/updmap.cfg) > > updmap [ERROR]: yhmath.map (in > > /usr/local/share/texmf/web2c/updmap.cfg) > > These are all activated in a local configuration file, so it is your > responsability. I don't recall every adding things in that file, so that's why I mentioned it. > Please remove these entries from your local updmap.cfg file and all > will work out. I have removed the /usr/local/share/texmf directory and now the upgrade worked :-) It did create the /usr/local/share/texmf directory again, but that is not issue :-) Tiger!P
Bug#818372: Problem when updating testing
I have a similar issue with tex-common ---8<--- Setting up tex-common (6.05) ... Running mktexlsr. This may take some time... done. Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in /tmp/updmap.0IcV1B8b Please include this file if you report a bug. Sometimes, not accepting conffile updates in /etc/texmf/updmap.d causes updmap-sys to fail. Please check for files with extension .dpkg-dist or .ucf-dist in this directory dpkg: error processing package tex-common (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of texlive-fonts-recommended: texlive-fonts-recommended depends on tex-common (>= 6); however: Package tex-common is not configured yet. dpkg: error processing package texlive-fonts-recommended (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of texlive-fonts-recommended-doc: texlive-fonts-recommended-doc depends on tex-common (>= 6); however: Package tex-common is not configured yet. dpkg: error processing package texlive-fonts-recommended-doc (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of texlive-latex-base: texlive-latex-base depends on tex-common (>= 6); however: Package tex-common is not configured yet. dpkg: error processing package texlive-latex-base (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of texlive-latex-base-doc: texlive-latex-base-doc depends on tex-common (>= 6); however: Package tex-common is not configured yet. dpkg: error processing package texlive-latex-base-doc (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of tipa: tipa depends on texlive-latex-base; however: Package texlive-latex-base is not configured yet. tipa depends on tex-common (>= 3); however: Package tex-common is not configured yet. dpkg: error processing package tipa (--configure): dependency problems - leaving unconfigured ---8<--- The contents of /tmp/updmap.0IcV1B8b: ---8<--- updmap will read the following updmap.cfg files (in precedence order): /usr/local/share/texmf/web2c/updmap.cfg /usr/share/texmf/web2c/updmap.cfg /usr/share/texlive/texmf-dist/web2c/updmap.cfg updmap may write changes to the following updmap.cfg file: /etc/texmf/web2c/updmap.cfg dvips output dir: "/var/lib/texmf/fonts/map/dvips/updmap" pdftex output dir: "/var/lib/texmf/fonts/map/pdftex/updmap" dvipdfmx output dir: "/var/lib/texmf/fonts/map/dvipdfmx/updmap" updmap [ERROR]: The following map file(s) couldn't be found: updmap [ERROR]: epiolmec.map (in /usr/local/share/texmf/web2c/updmap.cfg) updmap [ERROR]: esint.map (in /usr/local/share/texmf/web2c/updmap.cfg) updmap [ERROR]: stmaryrd.map (in /usr/local/share/texmf/web2c/updmap.cfg) updmap [ERROR]: xypic.map (in /usr/local/share/texmf/web2c/updmap.cfg) updmap [ERROR]: yhmath.map (in /usr/local/share/texmf/web2c/updmap.cfg) updmap [ERROR]: Did you run mktexlsr? You can disable non-existent map entries using the option --syncwithtrees. ---8<--- I can reproduce this issue at the moment when I install or update any package because the tex packages are not correctly installed. What can I do to help investigate the issue? Tiger!P
Bug#792807: apt-dater: Can't locate XML/Writer.pm when running apt-dater
Package: apt-dater Version: 1.0.2-1 Severity: normal Dear Maintainer, * What led up to the situation? apt-dater was updated to version 1.0.2-1 which uses a new config format. * What exactly did you do (or not do) that was effective (or ineffective)? After the update was done, I quit apt-dater and started it again. This gave me the following message: ** Message: Creating default config file /home/tigerp/.config/apt-dater/apt- dater.xml Can't locate XML/Writer.pm in @INC (you may need to install the XML::Writer module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.20.2 /usr/local/share/perl/5.20.2 /usr/lib/x86_64-linux-gnu/perl5/5.20 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at /usr/lib/x86_64-linux-gnu/apt-dater/hosts2xml line 8. BEGIN failed--compilation aborted at /usr/lib/x86_64-linux-gnu/apt- dater/hosts2xml line 8. ** Message: Creating default config file /home/tigerp/.config/apt- dater/hosts.xml ** Message: Creating default config file /home/tigerp/.config/apt- dater/tmux.conf * What outcome did you expect instead? I would not expect it to show the message I got. This is only shown the first time after the update. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-dater depends on: ii libc6 2.19-18 ii libglib2.0-02.44.1-1.1 ii libncursesw55.9+20150516-2 ii libpopt01.16-10 ii libtcl8.5 8.5.18-2 ii libtinfo5 5.9+20150516-2 ii libxml2 2.9.1+dfsg1-5 ii openssh-client 1:6.7p1-6 ii procmail3.22-25 ii tmux2.0-3 apt-dater recommends no packages. Versions of packages apt-dater suggests: ii apt-dater-host 1.0.0-2 ii xsltproc1.1.28-2+b2 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682021: avelsieve: PHP Parse error when using File backend
Package: avelsieve
Version: 1.9.9-2
Severity: important
Tags: upstream
When setting $avelsieve_backend = 'File'; in the config file, I get the
following in the apache error log, when I visit
http://example.com/squirrel/plugins/avelsieve/table.php:
PHP Parse error: syntax error, unexpected T_LIST, expecting T_STRING in
/usr/share/squirrelmail/plugins/avelsieve/include/DO_Sieve_File.class.php on
line 55,
This is also mentioned in ticket 252 [1] of avelsieve
[1] http://email.uoa.gr/avelsieve/ticket/252
-- System Information:
Debian Release: 6.0.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages avelsieve depends on:
ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy
ii libjs-scriptaculous 1.8.3-1JavaScript library for dynamic web
ii squirrelmail 2:1.4.21-2 Webmail for nuts
avelsieve recommends no packages.
Versions of packages avelsieve suggests:
ii dovecot-imapd 1:1.2.15-7 secure IMAP server that supports m
-- Configuration Files:
/etc/squirrelmail/avelsieve-config.php changed:
?php
/**
* User-friendly interface to SIEVE server-side mail filtering.
* Plugin for Squirrelmail 1.4+
*
* Licensed under the GNU GPL. For full terms see the file COPYING that came
* with the Squirrelmail distribution.
*
* This file contains configuration parameters for SIEVE mail filters plugin
* (aka avelsieve)
*
* @version $Id: config_sample.php 1025 2009-05-21 08:35:24Z avel $
* @author Alexandros Vellis a...@users.sourceforge.net
* @copyright 2002-2004 Alexandros Vellis
* @package plugins
* @subpackage avelsieve
*/
/**
* Debug Mode. Enable this (change to 1) if you need to send a bug report,
* or to 2 or 3 if you are a developer!
*
* Valid values:
* 0 = No debugging output
* 1 = Normal debugging output
* 2 = Firebug-enhanced debugging output
* 3 = Enhanced debugging output and no Sieve capabilities checks - enables
* all UI features!
*/
if(!defined('AVELSIEVE_DEBUG')) {
define('AVELSIEVE_DEBUG', 0);
}
/* */
/* === IMAP Server / SIEVE Setup = */
/* */
/** @var string Backend to use. Available backends are:
* 'ManageSieve': Uses the ManageSieve protocol. e.g. Cyrus
* 'File': Writes files straight to disk. e.g. Exim4, Dovecot LDA.
*/
global $avelsieve_backend;
// stefan 20120718 - We use Dovecot LDA
//$avelsieve_backend = 'ManageSieve';
$avelsieve_backend = 'File';
/* */
/* === ManageSieve Backend Options */
/* */
/* Port where timsieved listens on the Cyrus IMAP server. Default is 2000. */
/** DEBIAN CHANGE: Depsite upstream's intention Debian changed this default
* distribution wide to 4190 which is thus default here.
*/
global $sieveport;
$sieveport = 4190;
/**
* @var string Space separated list of preferred SASL mechanisms for the
* authentication to timsieved. e.g. PLAIN DIGEST-MD5;*/
global $sieve_preferred_sasl_mech;
$sieve_preferred_sasl_mech = 'PLAIN';
/**
* @var boolean Disable STARTTLS for ManageSieve. You can set this to true,
* if you do not wish to use encryption via TLS mechanisms (i.e. the server
* is not configured properly, or this is a local connection and TLS is not
* needed.
* Note that STARTTLS is supported only in PHP5+. In PHP4 this option will
* have no effect and STARTTLS will be disabled anyway.
*
* DEBIAN CHANGE:
* To properly work with a default cyrus installation on the same host as
* SquirrelMail $avelsieve_disabletls defaults to true.
*/
global $avelsieve_disabletls;
$avelsieve_disabletls = true;
/* */
/* === File Backend Options === */
/* */
global $avelsieve_file_backend_options, $data_dir, $username;
$avelsieve_file_backend_options = array(
'avelsieve_default_file' = $data_dir/$username.sievesource
);
/* */
/* == Implementation- and Server-Specific Options */
/* */
/* In Cyrus 2.3+, the notification action is a bit more complex than the
* others. The oldcyrus variable is for supporting the partially implemented
* notify extension implementation of Cyrus 2.3. If you have Cyrus 2.3,
* just set this to
Bug#671471: [patch] Workaround for pulse-alsa.conf file
Hello,
I was able to get audio from my system again after changing the
/usr/share/alsa/pulse-alsa.conf file, see the attached patch file.
Of course I don't know why the config file contains the lines which I
commented, but since it works for me I thought to share it.
Tiger!P
--
A random quote:
You can become used to anything if it goes on long enough.
--- /usr/share/alsa/pulse-alsa.conf.orig2012-02-19 13:55:05.0
+0100
+++ /usr/share/alsa/pulse-alsa.conf 2012-05-06 19:37:01.0 +0200
@@ -4,13 +4,13 @@
pcm.!default {
type pulse
- hint {
- show {
- @func refer
- name defaults.namehint.basic
- }
- description Playback/recording through the PulseAudio sound
server
- }
+# hint {
+# show {
+# @func refer
+# name defaults.namehint.basic
+# }
+# description Playback/recording through the PulseAudio sound
server
+# }
}
ctl.!default {
@@ -19,13 +19,13 @@
pcm.pulse {
type pulse
- hint {
- show {
- @func refer
- name defaults.namehint.basic
- }
- description Playback/recording through the PulseAudio sound
server
- }
+# hint {
+# show {
+# @func refer
+# name defaults.namehint.basic
+# }
+# description Playback/recording through the PulseAudio sound
server
+# }
}
ctl.pulse {
Bug#554239: New patch for init.d script and default file
Hello,
I have attached a new patch which will solve the problem for the usage
of milter-greylist with postfix (with a chrooted smtpd(8)).
--
A random quote:
Wees braaf. En als dat niet lukt, dan maar voorzichtig.
--- milter-greylist.init2011-07-20 20:16:20.517721477 +0200
+++ milter-greylist.init.new2011-07-20 20:37:51.041226517 +0200
@@ -66,6 +66,11 @@
chmod 755 /var/run/$PNAME
fi
+SOCKET_DIR=$(dirname ${SOCKET})
+if [ ! -d ${SOCKET_DIR} ]; then
+ mkdir -p ${SOCKET_DIR}
+fi
+
set -e
case $1 in
@@ -73,6 +78,13 @@
echo -n Starting $DESC:
start-stop-daemon --start --pidfile $PIDFILE --name $PNAME \
$NICE --oknodo --startas $DAEMON -- $OPTIONS $DOPTIONS
+ sleep 1
+ if [ -n $SOCKETMODE ]; then
+ chmod $SOCKETMODE $SOCKET;
+ fi;
+ if [ -n $SOCKETOWNER ]; then
+ chown $SOCKETOWNER $SOCKET;
+ fi;
echo $NAME.
;;
@@ -89,6 +101,13 @@
start-stop-daemon --start --pidfile $PIDFILE --name $PNAME \
$NICE --oknodo --startas $DAEMON -- $OPTIONS $DOPTIONS
+ sleep 1
+ if [ -n $SOCKETMODE ]; then
+ chmod $SOCKETMODE $SOCKET;
+ fi;
+ if [ -n $SOCKETOWNER ]; then
+ chown $SOCKETOWNER $SOCKET;
+ fi;
echo $NAME.
;;
@@ -107,6 +126,13 @@
start-stop-daemon --start --pidfile $PIDFILE --name $PNAME \
$NICE --oknodo --startas $DAEMON -- $OPTIONS $DOPTIONS
+ sleep 1
+ if [ -n $SOCKETMODE ]; then
+ chmod $SOCKETMODE $SOCKET;
+ fi;
+ if [ -n $SOCKETOWNER ]; then
+ chown $SOCKETOWNER $SOCKET;
+ fi;
echo $NAME.
;;
--- milter-greylist.default 2011-07-20 20:16:35.185728529 +0200
+++ milter-greylist.default.new 2011-07-20 20:36:46.949223578 +0200
@@ -14,3 +14,10 @@
# Other options
# OPTIONS=
+
+# To allow postfix smtpd to connect to socket,
+# uncomment the following two lines
+# SOCKET=/var/spool/postfix/milter-greylist/milter-greylist.sock
+# USER=greylist:postfix
+# SOCKETOWNER=greylist:postfix
+# SOCKETMODE=0660
Bug#634903: milter-greylist: please add support for geoip database
Package: milter-greylist Version: 4.3.9-1 Severity: wishlist Please add support for using the GeoIP databases (geoip-database). So that the geoipdb and racl greylist geoip option in the greylist.conf can be used. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages milter-greylist depends on: ii adduser 3.113 add and remove users and groups ii libc62.13-7 Embedded GNU C Library: Shared lib ii libmilter1.0.1 8.14.4-2+b1 Sendmail Mail Filter API (Milter) ii libspf2-21.2.9-4 library for validating mail sender Versions of packages milter-greylist recommends: ii postfix 2.8.3-1High-performance mail transport ag milter-greylist suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626838: gnome-panel segfaults when network cable is plugged-in
On Tue, May 17, 2011 at 05:56:07PM +0200, Josselin Mouette wrote: Le dimanche 15 mai 2011 à 21:27 +0200, Tiger!P a écrit : Package: gnome-panel Version: 2.30.2-2 Severity: normal When I plug-in my network cable, I see the icon of NetworkManager active, after that the gnome-panel disappears and stays away. It tries to restart, but keeps on segfaulting. What applets have you enabled? From what I can find I think I have the following applets enabled: Window Selector 2.30.2 Volume Applet 2.30.0 Clock 2.30.2 Laptop Battery (Power Management Preferences) NetworkManager Applet 0.8.1 Keyboard Preferences Show updates (Software Sources) Log out Shut down Is there a (cli) command that I can run to get the names of the applets that are enabled? I have run debsums for some packages and see some failed files in it. So I think it is not a gnome-panel problem. Please put this bug-report on on-hold until I investigated that problem. Tiger!P -- A random quote: The best way to keep a secret is to tell no one. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626838: gnome-panel segfaults when network cable is plugged-in
Package: gnome-panel Version: 2.30.2-2 Severity: normal When I plug-in my network cable, I see the icon of NetworkManager active, after that the gnome-panel disappears and stays away. It tries to restart, but keeps on segfaulting. From the /var/log/syslog: May 15 21:16:10 localhost NetworkManager[1374]: info (eth0): carrier now ON (device state 2) May 15 21:16:10 localhost kernel: [38936.338698] atl2: eth0 NIC Link is Up100 Mbps Full Duplex May 15 21:16:10 localhost NetworkManager[1374]: info (eth0): device state change: 2 - 3 (reason 40) May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) starting connection 'de horst 28 static' May 15 21:16:10 localhost NetworkManager[1374]: info (eth0): device state change: 3 - 4 (reason 0) May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 1 of 5 (Device Prepare) started... May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 1 of 5 (Device Prepare) complete. May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 2 of 5 (Device Configure) starting... May 15 21:16:10 localhost NetworkManager[1374]: info (eth0): device state change: 4 - 5 (reason 0) May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 2 of 5 (Device Configure) successful. May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 2 of 5 (Device Configure) complete. May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 3 of 5 (IP Configure Start) started... May 15 21:16:10 localhost NetworkManager[1374]: info (eth0): device state change: 5 - 7 (reason 0) May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 4 of 5 (IP4 Configure Get) scheduled... May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Beginning IP6 addrconf. May 15 21:16:10 localhost avahi-daemon[1449]: Withdrawing address record for fe80::223:54ff:fe34:9462 on eth0. May 15 21:16:10 localhost avahi-daemon[1449]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::223:54ff:fe34:9462. May 15 21:16:10 localhost avahi-daemon[1449]: Interface eth0.IPv6 no longer relevant for mDNS. May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 4 of 5 (IP4 Configure Get) started... May 15 21:16:10 localhost NetworkManager[1374]: info Activation (eth0) Stage 4 of 5 (IP4 Configure Get) complete. May 15 21:16:12 localhost avahi-daemon[1449]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::223:54ff:fe34:9462. May 15 21:16:12 localhost avahi-daemon[1449]: New relevant interface eth0.IPv6 for mDNS. May 15 21:16:12 localhost avahi-daemon[1449]: Registering new address record for fe80::223:54ff:fe34:9462 on eth0.*. May 15 21:16:13 localhost avahi-daemon[1449]: Leaving mDNS multicast group on interface eth0.IPv6 with address fe80::223:54ff:fe34:9462. May 15 21:16:13 localhost avahi-daemon[1449]: Joining mDNS multicast group on interface eth0.IPv6 with address 2001:888:148c:0:223:54ff:fe34:9462. May 15 21:16:13 localhost avahi-daemon[1449]: Registering new address record for 2001:888:148c:0:223:54ff:fe34:9462 on eth0.*. May 15 21:16:13 localhost avahi-daemon[1449]: Withdrawing address record for fe80::223:54ff:fe34:9462 on eth0. May 15 21:16:13 localhost NetworkManager[1374]: info Activation (eth0) Stage 4 of 5 (IP6 Configure Get) scheduled... May 15 21:16:13 localhost NetworkManager[1374]: info Activation (eth0) Stage 4 of 5 (IP6 Configure Get) started... May 15 21:16:13 localhost NetworkManager[1374]: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... May 15 21:16:13 localhost NetworkManager[1374]: info Activation (eth0) Stage 4 of 5 (IP6 Configure Get) complete. May 15 21:16:13 localhost NetworkManager[1374]: info Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... May 15 21:16:13 localhost avahi-daemon[1449]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.28.10. May 15 21:16:13 localhost avahi-daemon[1449]: New relevant interface eth0.IPv4 for mDNS. May 15 21:16:13 localhost avahi-daemon[1449]: Registering new address record for 192.168.28.10 on eth0.IPv4. May 15 21:16:15 localhost NetworkManager[1374]: info (eth0): device state change: 7 - 8 (reason 0) May 15 21:16:15 localhost NetworkManager[1374]: info Policy set 'de horst 28 static' (eth0) as default for IPv4 routing and DNS. May 15 21:16:15 localhost NetworkManager[1374]: info Policy set 'de horst 28 static' (eth0) as default for IPv6
Bug#623036: closed by Matthijs Möhlmann matth...@cacholong.nl (Bug#623036: fixed in pdns 2.9.22-9)
The bug has not been fixed in 2.9.22-9. I still get the same error message in the log. Is there anything else I can do to supply more information? Tiger!P -- A random quote: Een reden is alleen maar interessant als je het doel er van snapt. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579664: gconf2 2.28.1-6 upgrade fails
Package: gconf2 Version: 2.28.1-6 Severity: normal -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gconf2 depends on: ii dbus-x111.2.24-4 simple interprocess messaging syst ii gconf2-common 2.28.1-6 GNOME configuration database syste ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libgconf2-4 2.28.1-6 GNOME configuration database syste ii libglib2.0-02.24.2-1 The GLib library of C routines ii libxml2 2.7.8.dfsg-2 GNOME XML library ii psmisc 22.11-1 utilities that use the proc file s ii python 2.6.6-3+squeeze6 interactive high-level object-orie Versions of packages gconf2 recommends: ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface Versions of packages gconf2 suggests: ii gconf-defaults-service2.28.1-6 GNOME configuration database syste -- no debconf information I got the following messages when I tried to upgrade gconf2. root@localhost:~# aptitude install gconf2 The following partially installed packages will be configured: gconf2 gdm3 gnome-settings-daemon No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Setting up gconf2 (2.28.1-6) ... /usr/share/gconf/schemas/gedit-drawspaces.schemas:144: parser error : Specification mandate value for attribute n locale n!mesv ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:144: parser error : attributes construct error locale n!mesv ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:144: parser error : Couldn't find end of Start Tag locale line 144 locale n!mesv ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:144: parser error : PCDATA invalid Char value 29 locale n!mesv ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:146: parser error : Opening and ending tag mismatch: schema line 78 and hocale /hocale ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:149: parser error : expected '' short绘制跳格/short ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:149: parser error : StartTag: invalid element name short绘制跳格/short ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:151: parser error : Opening and ending tag mismatch: schemalist line 2 and schema /schema ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:154: parser error : Opening and ending tag mismatch: schema line 153 and key 4key/schemas/apps/gedit-2/plugins/drawspaces/dbaw_sPaces/key ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:155: parser error : Opening and ending tag mismatch: applyto line 155 and apply4o applyto/Apps/gedit-2/plugins/drawspaces/draw_spaces/apply4o ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:156: parser error : Opening and ending tag mismatch: oWner line 156 and owner oWnergedit/owner ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:157: parser error : Opening and ending tag mismatch: pype line 157 and type pypebool/type ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:158: parser error : Opening and ending tag mismatch: default line 158 and dedault defaultTRUE/dedault ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:161: parser error : Opening and ending tag mismatch: lncale line 159 and lnCale /lnCale ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:314: parser error : Opening and ending tag mismatch: gconfschemafile line 1 and schema /schema ^ /usr/share/gconf/schemas/gedit-drawspaces.schemas:316: parser error : Extra content at the end of the document schema ^ /usr/share/gconf/schemas/stickynotes.schemas:3008: parser error : Input is not proper UTF-8, indicate encoding ! Bytes: 0xC0 0x9F 0xC4 0xB1 n masaüstü üzerindeki tüm çalışma alanlarında görülebilir olup olmadı ^ /usr/share/gconf/schemas/stickynotes.schemas:3009: parser error : StartTag: invalid element name +locale ^ /usr/share/gconf/schemas/stickynotes.schemas:3013: parser error : PCDATA invalid Char value
Bug#623036: Wrong version reported
Hello, I saw in the bugtracker that it stated Found in version pdns/2.9.22-8, but that is not correct. The bug is in version 2.9.22-8+b1 . The reason it reported the other version, is that I first reverted to the previous version before running reportbug. Sorry Tiger!P -- A random quote: Wie zegt dat het leukste moment in je leven al niet voorbij is? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#623036: pdns-backend-mysql: pdns fails to start: Unable to load module '/usr/lib/powerdns/libgmysqlbackend.so'
Package: pdns-backend-mysql Version: 2.9.22-8+b1 Severity: grave Justification: renders package unusable I saw the following line in the daemon.log: Apr 16 21:33:14 sabrina pdns[4340]: Unable to load module '/usr/lib/powerdns/libgmysqlbackend.so': /usr/lib/powerdns/libgmysqlbackend.so: symbol __cxa_pure_virtual, version libmysqlclient_16 not defined in file libmysqlclient.so.16 with link time reference And pdns cannot start because of this. Now I have reverted to the previous version of the package (2.9.22-8) which starts. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pdns-backend-mysql depends on: pn libc6 none (no description available) ii libgcc1 1:4.6.0-2GCC support library ii libmysqlclient165.1.49-3 MySQL database client library ii libstdc++6 4.6.0-2 The GNU Standard C++ Library v3 ii pdns-server 2.9.22-8+b1 extremely powerful and versatile nameserver ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime pdns-backend-mysql recommends no packages. pdns-backend-mysql suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621363: linux-base: postinst fails when dosfslabel is not installed
Package: linux-base Version: 3 Severity: normal -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-base depends on: ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii libuuid-perl 0.02-4 Perl extension for using UUID inte ii udev 166-1 /dev/ and hotplug management daemo ii util-linux2.17.2-9.1 Miscellaneous system utilities linux-base recommends no packages. linux-base suggests no packages. -- debconf information: linux-base/disk-id-manual-boot-loader: linux-base/disk-id-update-failed: linux-base/disk-id-manual: * linux-base/disk-id-convert-plan-no-relabel: true * linux-base/disk-id-convert-auto: true linux-base/do-bootloader-default-changed: * linux-base/disk-id-convert-plan: true When upgrading the system with the following line in /etc/fstab, it fails because dosfslabel is not installed. /dev/sdc1 /mnt/sdc1 vfat sync,dirsync,noatime,users,noauto,rw,noexec,iocharset=iso8859-1,codepage=850,fmask=0133,shortname=lower 0 0 I got the following message: Configuring linux-base Failed to update disk device IDs An error occurred while attempting to update the system configuration: Can't exec dosfslabel: No such file or directory at /var/lib/dpkg/info/linux-base.postinst line 1046, STDIN line 10. dosfslabel failed: -1 at /var/lib/dpkg/info/linux-base.postinst line 1046, STDIN line 10. You can either correct this error and retry the automatic update, or choose to update the system configuration yourself. I would expect a normal message that the conversion can not be done, instead of the current message. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547669: Patch for vuurmuur.init script
Hello, Here a patch for the vuurmuur.init script that causes the upgrade problem. Tiger!P -- A random quote: Zonder de verstandhouding te kennen, kan je geen goede conclusies maken. --- vuurmuur.init.orig 2009-10-31 20:03:28.0 +0100 +++ vuurmuur.init 2009-10-31 20:03:47.0 +0100 @@ -102,7 +102,7 @@ if [ $(pidof vuurmuur) ] then - kill -n INT $(pidof vuurmuur) + kill -s INT $(pidof vuurmuur) echo done. else @@ -114,7 +114,7 @@ if [ $(pidof vuurmuur_log) ] then - kill -n INT $(pidof vuurmuur_log) + kill -s INT $(pidof vuurmuur_log) echo done. else
Bug#529893: Related to bug 511099
I think this bug is a result of bug 511099. You can work around the problem by copying all files from /usr/share/vuurmuur/services/ to /etc/vuurmuur/services Tiger!P -- A random quote: Het is altijd de zwakste schakel die het begeeft. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547669: upgrade vuurmuur fails because of problem with init script
Package: vuurmuur Version: 0.7+debian-1 Severity: important When I tried to upgrade vuurmuur to version vuurmuur_0.7+debian-2_i386 I got the following output: Preparing to replace vuurmuur 0.7+debian-1 (using .../vuurmuur_0.7+debian-2_i386.deb) ... Stopping Vuurmuur Firewall: - Stopping vuurmuur:kill: 147: Illegal option -n invoke-rc.d: initscript vuurmuur, action stop failed. dpkg: warning: old pre-removal script returned error exit status 2 dpkg - trying script from the new package instead ... Stopping Vuurmuur Firewall: - Stopping vuurmuur:kill: 147: Illegal option -n invoke-rc.d: initscript vuurmuur, action stop failed. dpkg: error processing /var/cache/apt/archives/vuurmuur_0.7+debian-2_i386.deb (--unpack): subprocess new pre-removal script returned error exit status 2 update-rc.d: warning: vuurmuur start runlevel arguments (S) do not match LSB Default-Start values (1 2 3 4 5) Starting Vuurmuur Firewall: - Loading modules: ip_tables iptable_filter iptable_mangle iptable_nat ip_conntrack ipt_state ip_conntrack_ftp ip_nat_ftp ip_queue. - Starting vuurmuur: already running. - Starting vuurmuur_log: already running. Errors were encountered while processing: /var/cache/apt/archives/vuurmuur_0.7+debian-2_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I think the upgrade should succeed normally. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i586) Kernel: Linux 2.6.30-1-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages vuurmuur depends on: ii libc6 2.9-26 GNU C Library: Shared libraries ii libvuurmuur00.7+debian-2 netfilter frontend (library) Versions of packages vuurmuur recommends: ii iptables1.4.4-2 administration tools for packet fi ii vuurmuur-conf 0.7+debian-2 netfilter frontend (ncurses GUI) vuurmuur suggests no packages. -- no debconf information Tiger!P -- A random quote: De winnaar geeft nooit op, de opgever wint nooit. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506544: /usr/bin/gnome-panel: Segfault for gnome-panel (debian-eee)
Package: gnome-panel Version: 2.20.3-5 Followup-For: Bug #506544 $ dpkg -l *-dbg|grep ^ii ii gnome-panel-dbg 2.20.3-5 GNOME Panel and library for panel applets - ii libgnomeui-0-dbg 2.20.1.1-2 The GNOME 2 libraries (User Interface) and d ii libgnomevfs2-0-dbg 1:2.22.0-5 GNOME Virtual File System (debugging librari ii libgtk2.0-0-dbg 2.12.12-1~lenny1 The GTK+ libraries and debugging symbols $ $ $ gdb /usr/bin/gnome-panel GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as i486-linux-gnu... (gdb) run Starting program: /usr/bin/gnome-panel Error while mapping shared library sections: /usr/lib/libgnomeui-2.so.0: not in executable format: File format not recognized. Error while mapping shared library sections: /usr/lib/libbonobo-2.so.0: not in executable format: File format not recognized. Error while mapping shared library sections: /usr/lib/libgnomevfs-2.so.0: not in executable format: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. [Thread debugging using libthread_db enabled] [New Thread 0xb6d54700 (LWP 12821)] Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomevfs-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libgnomeui-2.so.0: can't read symbols: File format not recognized. Error while reading shared library symbols: /usr/lib/libbonobo-2.so.0: can't read symbols: File format not recognized. Error while reading
Bug#511099: vuurmuur package does not install services in the right directory
Package: vuurmuur Version: 0.6+debian-1 The vuurmuur package does not install the services in /etc/vuurmuur/services, but in /usr/share/vuurmuur/services . This causes vuurmuur to have no services at all. Please install the services in /etc/vuurmuur/services, so that vuurmuur can be configured after installation. I'm using Debian unstable -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511107: libvuurmuur0 package does not install files with the right permissions
Package: libvuurmuur0 Version: 0.6+debian-1 After installing vuurmuur-conf I started vuurmuur_conf and got a lot of messages regarding the permissions of the files that were installed. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur/plugins/textdir.conf' is readable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur/' is readable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur/' is executable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur//services' is readable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur//services' is executable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur//zones' is readable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur//zones' is executable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur//interfaces' is readable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur//interfaces' is executable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur//rules' is readable by 'group' and 'other'. This is not recommended. Fixing. 01/06/2009 10:28:45 : PID 8724 : vuurmuur_conf : Info: '/etc/vuurmuur//rules' is executable by 'group' and 'other'. This is not recommended. Fixing. Because the file /etc/vuurmuur/plugins/textdir.conf is owned by libvuurmuur0, I file this report against this package. I suggest that the package installs the files in /etc/vuurmuur with 700 permissions. I'm using Debian unstable -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#365463: Acknowledgement (courier-authmysql cannot be installed because of a dependency (unstable))
This problem has been solved by the new courier-authlib-mysql package, which is now available for the unstable release. Tiger!P -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#365463: courier-authmysql cannot be installed because of a dependency (unstable)
Package: courier-authmysql Version: 0.47-13 When I try to install courier-authmysql on my unstable debian system I get the following error: # apt-get install courier-authmysql Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: courier-authmysql: Depends: libmysqlclient12 but it is not installable E: Broken packages # The unstable system has mysql-server-5.0 and other mysql-5.0 packages installed. If you need any other information, please let me know (and add the things I have to type to get the information, because I'm not really familiar with debian yet). Tiger!P -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
