Bug#1051938: Resolved with a reboot
Hello,
As an FYI: I downgraded systemd 253.5-1 but couldn't get it to function
("Failed to activate service 'org.freedesktop.systemd1'")
I eventually rebooted my system (ended up having to boot of a live
distro and fix the initramfs images which had all gotten broken during
the initial upgrade failure) and the problem has disappeared after that.
apt upgrade re-applied systemd 254.1-3 with no issues.
- Michel
Bug#1051938: systemd: "Assertion 'path_is_absolute(p)' failed" on upgrade
On 14/09/2023 19:55, Michael Biebl wrote: Am 14.09.23 um 19:52 schrieb Michael Biebl: Am 14.09.23 um 15:43 schrieb Michel Meyers: Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:628, function chase( ). Aborting. Sounds like https://github.com/systemd/systemd/issues/28458 Do you use any virtualization like OpenVZ ? No OpenVZ, but I do have both Docker containers and a VM in KVM/libvirt running on this box.
Bug#1051938: systemd: "Assertion 'path_is_absolute(p)' failed" on upgrade
Package: systemd
Version: 254.1-3
Severity: important
Dear Maintainer,
While running an apt upgrade, systemd fails to get upgraded/installed
with the followint error messages:
Setting up systemd (254.1-3) ...
Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:628, function
chase(
). Aborting.
/var/lib/dpkg/info/systemd.postinst: line 11: 3184727 Aborted
(c
ore dumped) journalctl ${DPKG_ROOT:+--root="$DPKG_ROOT"} --update-catalog
Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:628, function
chase(
). Aborting.
/var/lib/dpkg/info/systemd.postinst: line 65: 3184729 Aborted
(c
ore dumped) systemd-sysusers ${DPKG_ROOT:+--root="$DPKG_ROOT"} basic.conf
system
d-journal.conf systemd-network.conf
dpkg: error processing package systemd (--configure):
installed systemd package post-installation script subprocess returned error
ex
it status 134
I am uncertain on how to debug this further.
- Michel
*** End of the template - remove these template lines ***
-- Package-specific info:
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.4.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
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 not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii libacl12.3.1-3
ii libaudit1 1:3.1.1-1
ii libblkid1 2.39.2-1
ii libc6 2.37-7
ii libcap21:2.66-4
ii libcryptsetup122:2.6.1-5
ii libfdisk1 2.39.2-1
ii libgcrypt201.10.2-2
ii libkmod2 30+20230601-1
ii liblz4-1 1.9.4-1
ii liblzma5 5.4.4-0.1
ii libmount1 2.39.2-1
ii libp11-kit00.25.0-4
ii libseccomp22.5.4-1+b3
ii libselinux13.5-1
ii libssl33.0.10-1
ii libsystemd-shared 254.1-3
ii libsystemd0254.1-3
ii libzstd1 1.5.5+dfsg2-1
ii mount 2.39.2-1
ii systemd-dev254.1-3
Versions of packages systemd recommends:
ih dbus [default-dbus-system-bus] 1.14.10-1
ii ntpsec [time-daemon]1.2.2+dfsg1-2
Versions of packages systemd suggests:
ii libfido2-11.13.0-1
ii libqrencode4 4.1.1-1
ii libtss2-esys-3.0.2-0 3.2.1-3
ii libtss2-mu0 3.2.1-3
pn libtss2-rc0
ii polkitd 123-1
ii python3 3.11.4-5+b1
pn python3-pefile
pn systemd-boot
ii systemd-container 254.1-3
pn systemd-homed
pn systemd-resolved
pn systemd-userdbd
Versions of packages systemd is related to:
ii dbus-user-session 1.14.10-1
pn dracut
it initramfs-tools0.142
ii libnss-systemd 254.1-3
ii libpam-systemd 254.1-3
ih udev 254.1-3
-- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=ignore
-- no debconf information
Assertion 'path_is_absolute(p)' failed at src/basic/chase.c:628, function
chase(). Aborting.
Failed to call DumpByFileDescriptor: Failed to activate service
'org.freedesktop.systemd1': timed out (service_start_timeout=25000ms)
==> /var/lib/systemd/deb-systemd-helper-enabled/snapd.apparmor.service.dsh-also
<==
Bug#983750: [Pkg-utopia-maintainers] Bug#983750: networkmanager: NM takes over slave interfaces of bond
On 2021-03-01 16:02, Michael Biebl wrote: > Am 01.03.21 um 13:59 schrieb Michel Meyers: > >> # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) >> >> # The loopback interface >> auto lo >> iface lo inet loopback >> >> # The first network card - this entry was created during the Debian >> installation >> # (network, broadcast and gateway are optional) >> #auto eth0 >> auto bond0 >> iface bond0 inet static >> address 192.168.1.2 >> netmask 255.255.255.0 >> gateway 192.168.1.1 >> mtu 9000 >> slaves ens6 eth1 > > > > Reading https://www.commandlinux.com/man-page/man5/interfaces.5.html , > it appears "slave" is no native ifupdown config stanza. > I suppose it is implemented by a third party package? Guessing its Debian specific? I got it from here: https://wiki.debian.org/Bonding#Configuration_-_Example_1 - Michel
Bug#983750: [Pkg-utopia-maintainers] Bug#983750: networkmanager: NM takes over slave interfaces of bond
On 2021-03-01 12:22, Michael Biebl wrote: Am 01.03.21 um 11:56 schrieb Michel Meyers: I have now created [device] sections declaring the slaves as managed=0 in the NetworkManager.conf (left over after uninstalling NM), but anyone with the same config as me making the same mistake of inadvertently installing NM will land in the same weird situation where their bond0 interface is up but not getting its slaves. (I've also started looking at specifically declaring the slave interfaces in /etc/network/interfaces, but not had success with that so far as it stops the bond0 interface from coming up correctly. "Example 2" from the docs seems broken here ... more debugging to be done.) Trying to parse and interpret /etc/network/interfaces in NetworkManager is a losing battle I fear. We have some support to understand basic ifupdown configurations, but it's incomplete and buggy. Can you share your /e/n/i? Sure: -- # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) #auto eth0 auto bond0 iface bond0 inet static address 192.168.1.2 netmask 255.255.255.0 gateway 192.168.1.1 mtu 9000 slaves ens6 eth1 bond-mode active-backup bond-miimon 100 bond-downdelay 200 bond-updelay 200 post-up route add 192.168.0.1 gw 192.168.1.147 && ip route add 1.1.1.1 via 192.168.1.11 && ip route add 1.0.0.1 via 192.168.1.12 pre-down route del 192.168.0.1 gw 192.168.1.147 && ip route del 1.1.1.1 via 192.168.1.11 && ip route del 1.0.0.1 via 192.168.1.12 iface bond0 inet6 auto privext 2 auto bond0:0 allow-hotplug bond0:0 iface bond0:0 inet static address 192.168.1.5 netmask 255.255.255.0 iface bond0:0 inet6 auto privext 2 -- My guess is that the fact that there's no iface definition for the slaves (ens6 and eth1) caused them to be taken over by NM. (The only indication NM could've had to avoid them is the "slaves" stanza within the bond0 iface definition.) I've since tried to re-define them like this: -- # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface auto lo iface lo inet loopback # The first network card - this entry was created during the Debian installation # (network, broadcast and gateway are optional) #auto eth0 auto bond0 iface bond0 inet static address 192.168.1.200 netmask 255.255.255.0 gateway 192.168.1.1 mtu 9000 bond-slaves ens6 eth1 bond-primary ens6 bond-mode active-backup bond-miimon 100 bond-downdelay 200 bond-updelay 200 post-up route add 192.168.0.1 gw 192.168.1.1 && ip route add 1.1.1.1 via 192.168.1.11 && ip route add 1.0.0.1 via 192.168.1.12 pre-down route del 192.168.0.1 gw 192.168.1.1 && ip route del 1.1.1.1 via 192.168.1.11 && ip route del 1.0.0.1 via 192.168.1.12 iface bond0 inet6 auto privext 2 auto ens6 allow-bond ens6 iface ens6 inet manual bond-master bond0 auto eth1 allow-bond eth1 iface eth1 inet manual bond-master bond0 auto bond0:0 allow-hotplug bond0:0 iface bond0:0 inet static address 192.168.1.5 netmask 255.255.255.0 iface bond0:0 inet6 auto privext 2 -- But that fails with: -- Mar 1 10:15:07 server ifup[69522]: No iface stanza found for master bond0 Mar 1 10:15:07 server ifup[69518]: run-parts: /etc/network/if-pre-up.d/ifenslave exited with return code 1 Mar 1 10:15:07 server ifup[69516]: ifup: failed to bring up ens6 -- I have yet to figure out why the ifenslave check fails. (Seems to be running 'ifstate -l "$IF_BOND_MASTER"': ifstate is not a command that's in my path and the only ifstate script that I found in /usr/share/doc/ifupdown/contrib/ifstate doesn't take -l as a parameter. Maybe some package versions are out of sync on my system.) tl;dr: If it's easy to catch the 'slaves' stanza in /e/n/i and have NM consider the specified slaves as unmanaged, that would be nice, but the occurrence of this issue is admittedly very rare and thus may not be worth the effort. - Michel
Bug#983750: [Pkg-utopia-maintainers] Bug#983750: networkmanager: NM takes over slave interfaces of bond
On 2021-03-01 11:27, Michael Biebl wrote: Am 01.03.21 um 10:41 schrieb Andrei POPESCU: Control: reassign -1 network-manager On Lu, 01 mar 21, 10:00:26, Michel Meyers wrote: Package: networkmanager Severity: normal Dear Maintainer, I had a bond configured as described in Example 1 on: https://wiki.debian.org/Bonding This morning, my server's bond interface showed down, and its slaves kept getting removed. After some digging, I found that networkmanager had gotten installed and a check in nmcli showed that it had taken over each of the slave interfaces while listing bond0 as unmanaged. It appears that NM ignores the "slaves eth0 eth1" directive in /etc/network/interfaces so unless each of the interfaces is specifically named as in Example 2, NM takes over the slaves, killing the bond. If you want to prevent NM to "auto" manage your devices, you could use /usr/share/doc/network-manager/examples/server.conf (copy it to /etc/NetworkManager/conf.d/) Alternative, you can tell NM explicitly which devices it should ignore. See man NetworkManager.conf → unmanaged-devices I don't normally use NM and don't have it installed. It must've gotten pulled in as a dependency of some package (my fault for not catching it really) and the nightly systemd restart of services then somehow caused it to take over. I have now created [device] sections declaring the slaves as managed=0 in the NetworkManager.conf (left over after uninstalling NM), but anyone with the same config as me making the same mistake of inadvertently installing NM will land in the same weird situation where their bond0 interface is up but not getting its slaves. (I've also started looking at specifically declaring the slave interfaces in /etc/network/interfaces, but not had success with that so far as it stops the bond0 interface from coming up correctly. "Example 2" from the docs seems broken here ... more debugging to be done.) - Michel
Bug#983750: networkmanager: NM takes over slave interfaces of bond
Package: networkmanager Severity: normal Dear Maintainer, I had a bond configured as described in Example 1 on: https://wiki.debian.org/Bonding This morning, my server's bond interface showed down, and its slaves kept getting removed. After some digging, I found that networkmanager had gotten installed and a check in nmcli showed that it had taken over each of the slave interfaces while listing bond0 as unmanaged. It appears that NM ignores the "slaves eth0 eth1" directive in /etc/network/interfaces so unless each of the interfaces is specifically named as in Example 2, NM takes over the slaves, killing the bond. - Michel -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-3-amd64 (SMP w/12 CPU threads) 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 not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#945920: Random Chromium crashes
Hello, Been running Chromium for the last 6 hours now, no crash since, so it looks like that last patch finally got it. - Michel
Bug#945920: Random Chromium crashes
Hello, Same here unfortunately. It has fixed the SIGSEGV when opening the Task Manager, but as feared, that crash seems to be separate from the randomly occurring one. - Michel
Bug#945920: Chromium segfaults - backtraces
Thanks to Jaap Joris Vens for helping me figure out why my dumb ass couldn't find the debug package with apt-cache (they're in a separate repo now as the README points out). I've discovered two interesting things, the first one is possibly unrelated: 1. I can reliably cause Chromium to SIGSEGV by opening the Task Manager (Ctrl+Esc). Here's a backtrace from such a crash: Thread 1 "chromium" received signal SIGSEGV, Segmentation fault. 0x5a77cf87 in memory_instrumentation::MemoryInstrumentation::RequestPrivateMemoryFootprint(int, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) () (gdb) bt #0 0x5a77cf87 in memory_instrumentation::MemoryInstrumentation::RequestPrivateMemoryFootprint(int, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) () #1 0x591baaa9 in task_manager::TaskManagerImpl::Refresh() () #2 0x593e7c76 in base::RepeatingTimer::RunUserTask() () #3 0x593b5165 in base::TaskAnnotator::RunTask(char const*, base::PendingTask*) () #4 0x593c466b in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*, bool*) () #5 0x593c5fec in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() () #6 0x59376aca in base::(anonymous namespace)::WorkSourceDispatch(_GSource*, int (*)(void*), void*) () #7 0x77064f2e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x770651c8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7706525c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x59376dd0 in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) () #11 0x593c62a9 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run(bool, base::TimeDelta) () #12 0x593a22fa in base::RunLoop::Run() () #13 0x58ea8217 in ChromeBrowserMainParts::MainMessageLoopRun(int*) () #14 0x571cd1c6 in content::BrowserMainLoop::RunMainMessageLoopParts() () #15 0x571cd375 in content::BrowserMainRunnerImpl::Run() () #16 0x571a35f7 in content::BrowserMain(content::MainFunctionParams const&) () #17 0x58e30101 in content::RunBrowserProcessMain(content::MainFunctionParams const&, content::ContentMainDelegate*) () #18 0x58e30338 in content::ContentMainRunnerImpl::RunServiceManager(content::MainFunctionParams&, bool) () #19 0x58e306a7 in content::ContentMainRunnerImpl::Run(bool) () #20 0x58e66802 in service_manager::Main(service_manager::MainParams const&) () #21 0x58e2e0c6 in content::ContentMain(content::ContentMainParams const&) () #22 0x5635c3e5 in ChromeMain () #23 0x704a1bbb in __libc_start_main (main= 0x56339f80 , argc=1, argv=0x7fffe168, init=out>, fini=, rtld_fini=, stack_end=0x7fffe158) at ../csu/libc-start.c:308 #24 0x5635c22a in _start () (gdb) Might be an unrelated issue though. 2. While running in gbd and watching a YouTube video in full screen, I tried to pause it and couldn't (no cursor, YouTube UI not showing up), only to find it had segfaulted randomly. The video continued to play until I killed the process. This is that backtrace: Thread 1 "chromium" received signal SIGSEGV, Segmentation fault. 0x5a77cee7 in memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vectorstd::char_traits, std::allocator >, std::allocator, std::allocator > > > const&, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) () (gdb) bt #0 0x5a77cee7 in memory_instrumentation::MemoryInstrumentation::RequestGlobalDump(std::vectorstd::char_traits, std::allocator >, std::allocator, std::allocator > > > const&, base::OnceCallbackstd::unique_ptrstd::default_delete >)>) () #1 0x58f8ddb0 in ProcessMemoryMetricsEmitter::FetchAndEmitProcessMemoryMetrics() () #2 0x58f85e82 in (anonymous namespace)::RecordMemoryMetrics() () #3 0x593b5165 in base::TaskAnnotator::RunTask(char const*, base::PendingTask*) () #4 0x593c466b in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl(base::sequence_manager::LazyNow*, bool*) () #5 0x593c5fec in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoSomeWork() () #6 0x59376aca in base::(anonymous namespace)::WorkSourceDispatch(_GSource*, int (*)(void*), void*) () #7 0x77064f2e in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x770651c8 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7706525c in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #10 0x59376dd0 in base::MessagePumpGlib::Run(base::MessagePump::Delegate*) () #11 0x593c62a9 in
Bug#945920: Chromium randomly crashes in the latest version.
Package: chromium Version: 79.0.3945.79-1 Followup-For: Bug #945920 Hello, Seeing these crashes too. HP Elitebook 8470p with Intel i5-3320M and integrated Intel GPU. Running Xfce4. Hopefully the package info is useful in debugging. - Michel -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (550, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 chromium depends on: ii chromium-common 79.0.3945.79-1 ii libasound2 1.1.8-1 ii libatk-bridge2.0-0 2.30.0-5 ii libatk1.0-0 2.30.0-2 ii libatomic1 8.3.0-6 ii libatspi2.0-02.30.0-7 ii libavcodec58 7:4.2.1-2 ii libavformat587:4.2.1-2 ii libavutil56 7:4.2.1-2 ii libc62.29-3 ii libcairo-gobject21.16.0-4 ii libcairo21.16.0-4 ii libcups2 2.2.10-6+deb10u1 ii libdbus-1-3 1.12.16-1 ii libdrm2 2.4.97-1 ii libevent-2.1-7 2.1.11-stable-1 ii libexpat12.2.6-2+deb10u1 ii libflac8 1.3.2-3 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.10.1-2 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libharfbuzz0b2.3.1-1 ii libicu63 63.1-6 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libjsoncpp1 1.7.4-3 ii liblcms2-2 2.9-3 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.20-1 ii libnss3 2:3.42.1-1+deb10u2 ii libopenjp2-7 2.3.0-2 ii libopus0 1.3-1 ii libpango-1.0-0 1.42.4-7~deb10u1 ii libpangocairo-1.0-0 1.42.4-7~deb10u1 ii libpci3 1:3.5.2-1 ii libpng16-16 1.6.36-6 ii libpulse012.2-4+deb10u1 ii libre2-5 20190101+dfsg-2 ii libsnappy1v5 1.1.7-1 ii libstdc++6 9.2.1-21 ii libva2 2.5.0-2 ii libvpx6 1.8.1-2 ii libwebp6 0.6.1-2 ii libwebpdemux20.6.1-2 ii libwebpmux3 0.6.1-2+b1 ii libx11-6 2:1.6.7-1 ii libx11-xcb1 2:1.6.7-1 ii libxcb1 1.13.1-2 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-2 ii libxdamage1 1:1.1.4-3+b3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml2 2.9.4+dfsg1-7+b3 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.32-2.2~deb10u1 ii libxss1 1:1.2.3-1 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.11.dfsg-1 Versions of packages chromium recommends: ii chromium-sandbox 78.0.3904.108-1~deb10u1 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell Versions of packages chromium-common depends on: ii x11-utils 7.7+4 ii xdg-utils 1.1.3-1 Versions of packages chromium-common recommends: ii chromium-sandbox 78.0.3904.108-1~deb10u1 ii fonts-liberation 1:1.07.4-9 ii libgl1-mesa-dri 18.3.6-2 ii libu2f-udev 1.1.9-1 ii notification-daemon 3.20.0-4 ii system-config-printer1.5.11-4 ii upower 0.99.10-1 ii xfce4-notifyd [notification-daemon] 0.4.3-1 Versions of packages chromium-sandbox depends on: ii libatomic1 8.3.0-6 ii libc6 2.29-3 ii libgcc1 1:8.3.0-6 ii libstdc++6 9.2.1-21 -- no debconf information
Bug#939845:
On 2019-10-02 19:25, Daniel Kahn Gillmor wrote: If anyone has any clearer diagnostics about what version of wireguard introduced the errors for the older kernels, or (even better) what specific change seems to cause the incompatibility, then that might be useful for further debugging. I actually found wireguard-dkms_0.0.20190123-1_all.deb on the affected server indicating that I'd previously manually installed and used it. Trying to compile it fails with the same error, making me think that the problem cause is somewhere outside of Wireguard itself. - Michel
Bug#939845:
On 2019-10-02 10:05, Aron Xu wrote: I tried more to reproduce this bug, the problem only affect linux 4.19.0-0.bpo.4 and 4.19.0-0.bpo.5 (while I haven't tried earlier bpo versions), and does not affect 4.9 or 4.19.0-0.bpo.6 Since the affecting surface is small so far, I would suggest anyone run into this problem on stretch(-bpo) to upgrade to 4.19.0-0.bpo.6, it does not matter whether the kernel is the current running one at the time wireguard.ko is built. In my case, the machine is running buster (10.1) with these packages installed: :~# dpkg -l 'linux-headers-*' 'linux-image-*' 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) ||/ NameVersion Architecture Description +++-===---= ii linux-headers-4.12.0-2-amd644.12.13-1amd64 Header files for Linux 4.12.0-2-amd64 ii linux-headers-4.12.0-2-common 4.12.13-1all Common header files for Linux 4.12.0-2 ii linux-headers-4.14.0-3-amd644.14.17-1amd64 Header files for Linux 4.14.0-3-amd64 ii linux-headers-4.14.0-3-common 4.14.17-1all Common header files for Linux 4.14.0-3 ii linux-headers-4.19.0-2-amd644.19.16-1amd64 Header files for Linux 4.19.0-2-amd64 ii linux-headers-4.19.0-2-common 4.19.16-1all Common header files for Linux 4.19.0-2 ri linux-headers-4.19.0-4-amd644.19.28-2amd64 Header files for Linux 4.19.0-4-amd64 ri linux-headers-4.19.0-4-common 4.19.28-2all Common header files for Linux 4.19.0-4 ii linux-headers-4.19.0-5-amd644.19.37-5amd64 Header files for Linux 4.19.0-5-amd64 ii linux-headers-4.19.0-5-common 4.19.37-5all Common header files for Linux 4.19.0-5 ii linux-headers-4.19.0-6-amd644.19.67-2amd64 Header files for Linux 4.19.0-6-amd64 ii linux-headers-4.19.0-6-common 4.19.67-2all Common header files for Linux 4.19.0-6 un linux-headers-686-pae (no description available) ii linux-headers-amd64 4.19+105+deb10u1 amd64 Header files for Linux amd64 configuration (meta-package) un linux-headers-generic (no description available) rc linux-image-4.0.0-2-amd64 4.0.8-2 amd64 Linux 4.0 for 64-bit PCs rc linux-image-4.1.0-1-amd64 4.1.3-1 amd64 Linux 4.1 for 64-bit PCs rc linux-image-4.1.0-2-amd64 4.1.6-1 amd64 Linux 4.1 for 64-bit PCs rc linux-image-4.11.0-1-amd64 4.11.6-1 amd64 Linux 4.11 for 64-bit PCs rc linux-image-4.12.0-1-amd64 4.12.6-1 amd64 Linux 4.12 for 64-bit PCs rc linux-image-4.12.0-2-amd64 4.12.13-1amd64 Linux 4.12 for 64-bit PCs rc linux-image-4.13.0-1-amd64 4.13.13-1amd64 Linux 4.13 for 64-bit PCs rc linux-image-4.14.0-2-amd64 4.14.7-1 amd64 Linux 4.14 for 64-bit PCs rc linux-image-4.14.0-3-amd64 4.14.17-1amd64 Linux 4.14 for 64-bit PCs rc linux-image-4.15.0-2-amd64 4.15.11-1amd64 Linux 4.15 for 64-bit PCs rc linux-image-4.15.0-3-amd64 4.15.17-1amd64 Linux 4.15 for 64-bit PCs rc linux-image-4.16.0-1-amd64 4.16.5-1 amd64 Linux 4.16 for 64-bit PCs rc linux-image-4.16.0-2-amd64 4.16.16-2amd64 Linux 4.16 for 64-bit PCs rc linux-image-4.17.0-1-amd64 4.17.8-1 amd64 Linux 4.17 for 64-bit PCs rc linux-image-4.17.0-3-amd64 4.17.17-1amd64 Linux 4.17 for 64-bit PCs rc linux-image-4.18.0-1-amd64 4.18.6-1 amd64 Linux 4.18 for 64-bit PCs rc linux-image-4.18.0-2-amd64 4.18.10-2+b1 amd64 Linux 4.18 for 64-bit PCs rc linux-image-4.18.0-3-amd64 4.18.20-2amd64 Linux 4.18 for 64-bit PCs rc linux-image-4.19.0-1-amd64 4.19.12-1amd64 Linux 4.19 for 64-bit PCs (signed) un linux-image-4.19.0-1-amd64-unsigned (no description available) ii linux-image-4.19.0-2-amd64 4.19.16-1amd64 Linux 4.19 for 64-bit PCs (signed) un linux-image-4.19.0-2-amd64-unsigned (no description available) ii linux-image-4.19.0-4-amd64 4.19.28-2amd64 Linux 4.19 for 64-bit PCs (signed) un linux-image-4.19.0-4-amd64-unsigned (no description available) ii linux-image-4.19.0-5-amd64 4.19.37-5amd64
Bug#939845: modprobe: ERROR: could not insert 'wireguard': Exec format error
Hello, I'm seeing the same issue with kernel 4.19.0-2-amd64. Trying to manually compile the module also gives this result: root@server:/usr/src/wireguard-0.0.20190905# uname -a Linux server 4.19.0-2-amd64 #1 SMP Debian 4.19.16-1 (2019-01-17) x86_64 GNU/Linux root@server:/usr/src/wireguard-0.0.20190905# make module ver="#define WIREGUARD_VERSION \"\"" && \ [ "$(cat version.h 2>/dev/null)" != "$ver" ] && \ echo "$ver" > version.h || true CC [M] /usr/src/wireguard-0.0.20190905/main.o CC [M] /usr/src/wireguard-0.0.20190905/noise.o CC [M] /usr/src/wireguard-0.0.20190905/device.o CC [M] /usr/src/wireguard-0.0.20190905/peer.o CC [M] /usr/src/wireguard-0.0.20190905/timers.o CC [M] /usr/src/wireguard-0.0.20190905/queueing.o CC [M] /usr/src/wireguard-0.0.20190905/send.o CC [M] /usr/src/wireguard-0.0.20190905/receive.o CC [M] /usr/src/wireguard-0.0.20190905/socket.o CC [M] /usr/src/wireguard-0.0.20190905/peerlookup.o CC [M] /usr/src/wireguard-0.0.20190905/allowedips.o CC [M] /usr/src/wireguard-0.0.20190905/ratelimiter.o CC [M] /usr/src/wireguard-0.0.20190905/cookie.o CC [M] /usr/src/wireguard-0.0.20190905/netlink.o CC [M] /usr/src/wireguard-0.0.20190905/crypto/zinc/chacha20/chacha20.o PERLASM /usr/src/wireguard-0.0.20190905/crypto/zinc/chacha20/chacha20-x86_64.S AS [M] /usr/src/wireguard-0.0.20190905/crypto/zinc/chacha20/chacha20-x86_64.o CC [M] /usr/src/wireguard-0.0.20190905/crypto/zinc/poly1305/poly1305.o PERLASM /usr/src/wireguard-0.0.20190905/crypto/zinc/poly1305/poly1305-x86_64.S AS [M] /usr/src/wireguard-0.0.20190905/crypto/zinc/poly1305/poly1305-x86_64.o CC [M] /usr/src/wireguard-0.0.20190905/crypto/zinc/chacha20poly1305.o CC [M] /usr/src/wireguard-0.0.20190905/crypto/zinc/blake2s/blake2s.o AS [M] /usr/src/wireguard-0.0.20190905/crypto/zinc/blake2s/blake2s-x86_64.o CC [M] /usr/src/wireguard-0.0.20190905/crypto/zinc/curve25519/curve25519.o LD [M] /usr/src/wireguard-0.0.20190905/wireguard.o Building modules, stage 2. MODPOST 1 modules CC /usr/src/wireguard-0.0.20190905/wireguard.mod.o LD [M] /usr/src/wireguard-0.0.20190905/wireguard.ko root@server:/usr/src/wireguard-0.0.20190905# insmod wireguard.ko insmod: ERROR: could not insert module wireguard.ko: Invalid module format root@server:/usr/src/wireguard-0.0.20190905# dmesg -T [Fri Sep 20 09:58:36 2019] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 69137dca, val c10f4086 -- Michel
Bug#922062: ca-certificates package post-installation script subprocess returned error exit status 1
On 2019-02-11 20:43, Michael Shuler wrote: Thanks for the debugging info. I tried to reproduce a non-zero exit from both the old c_rehash and new openssl rehash calls, in order to see if we've found another behavior difference, but each call ended up with a clean 0 exit for me with a key file in the same place. I put that keyfile back in and immediately get the code 1 exit again: shodan:/etc/ssl/certs# openssl rehash . rehash: warning: skipping ca-certificates.crt,it does not contain exactly one certificate or CRL shodan:/etc/ssl/certs# echo $? 1 There's no warning about that particular pem file. The file is very old (dates from 2003-05-05 and is 1679 bytes in size for a 2048 key), so it must've been lying around there for a while. That would mean that some more or less recent change in OpenSSL (between this version of ca-certificates and the previous one) is causing the new exit code. (The file also isn't referenced in any of my configs, so I don't even know which cert, if any, it goes with. There's a subdirectory in /etc/ssl/certs called stunnel-trusted and it contains a cert from the same day called stunnel-client.pem, but the modulus doesn't match with the key. I can only guess that this is a remnant of me playing around with stunnel back when I was oblivious about how any of OpenSSL or even Linux worked.) - Michel
Bug#922062: ca-certificates package post-installation script subprocess returned error exit status 1
dpkg --debug=65535 shows this: - Setting up ca-certificates (20190110) ... D02: trigproc_activate_packageprocessing pkg=ca-certificates:all D02: fork/exec /var/lib/dpkg/info/ca-certificates.postinst ( configure 20170717 ) Updating certificates in /etc/ssl/certs... dpkg: error processing package ca-certificates (--install): installed ca-certificates package post-installation script subprocess returned error exit status 1 D02: post_script_tasks - ensure_diversions - Running the postinst myself I see no real errors, but still get a returncode 1 at the end: - export DEBCONF_DEBUG=developer /usr/share/debconf/frontend /var/lib/dpkg/info/ca-certificates.postinst configure 20170717 [...] debconf (developer): <-- FSET ca-certificates/new_crts seen false debconf (developer): --> 0 false debconf (developer): <-- STOP Updating certificates in /etc/ssl/certs... shodan:/# echo $? 1 - Running update-ca-certificates: shodan:/# update-ca-certificates -v Updating certificates in /etc/ssl/certs... Doing . link D-TRUST_Root_Class_3_CA_2_EV_2009.pem -> d4dae3dd.0 link Amazon_Root_CA_1.pem -> ce5e74ef.0 link GLC.pem -> 9871e719.0 link Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem -> 3bde41ac.0 link Certum_Trusted_Network_CA_2.pem -> 40193066.0 link Global_Chambersign_Root_-_2008.pem -> 0c4c9b6c.0 link Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015.pem -> 7719f463.0 link COMODO_Certification_Authority.pem -> 40547a79.0 link VeriSign_Class_3_Public_Primary_Certification_Authority_-_G4.pem -> 7d0b38bd.0 link EE_Certification_Centre_Root_CA.pem -> 128805a3.0 link LuxTrust_Global_Root_2.pem -> def36a68.0 link AC_RAIZ_FNMT-RCM.pem -> cd8c0d63.0 link DigiCert_Assured_ID_Root_CA.pem -> b1159c4c.0 link dovecot.pem -> f2d65788.0 link Buypass_Class_2_Root_CA.pem -> 54657681.0 link Amazon_Root_CA_4.pem -> de6d66f3.0 link Buypass_Class_3_Root_CA.pem -> e8de2f56.0 link thawte_Primary_Root_CA_-_G3.pem -> ba89ed3b.0 link VeriSign_Universal_Root_Certification_Authority.pem -> c01cdfa2.0 link Staat_der_Nederlanden_Root_CA_-_G3.pem -> 5a4d6896.0 link GlobalSign_ECC_Root_CA_-_R4.pem -> b0e59380.0 link Hellenic_Academic_and_Research_Institutions_RootCA_2011.pem -> 1636090b.0 link T-TeleSec_GlobalRoot_Class_2.pem -> 1e09d511.0 link TrustCor_RootCert_CA-2.pem -> 3e44d2f7.0 link Hellenic_Academic_and_Research_Institutions_RootCA_2015.pem -> 32888f65.0 link GlobalSign_Root_CA_-_R3.pem -> 062cdee6.0 link GeoTrust_Primary_Certification_Authority_-_G3.pem -> e2799e36.0 link ePKI_Root_Certification_Authority.pem -> ca6e4ad9.0 link QuoVadis_Root_CA_3_G3.pem -> e18bfb83.0 link ISRG_Root_X1.pem -> 4042bcee.0 link Starfield_Services_Root_Certificate_Authority_-_G2.pem -> 09789157.0 link TeliaSonera_Root_CA_v1.pem -> 5cd81ad7.0 link SZAFIR_ROOT_CA2.pem -> fe8a2cd8.0 link Amazon_Root_CA_2.pem -> 6d41d539.0 link ssl-cert-snakeoil.pem -> 2b97fccc.0 link Go_Daddy_Root_Certificate_Authority_-_G2.pem -> cbf06781.0 link COMODO_ECC_Certification_Authority.pem -> eed8c118.0 link Staat_der_Nederlanden_Root_CA_-_G2.pem -> 5c44d531.0 link Sonera_Class_2_Root_CA.pem -> 9c2e7d30.0 link Trustis_FPS_Root_CA.pem -> d853d49e.0 link SecureTrust_CA.pem -> f39fc864.0 link GeoTrust_Universal_CA_2.pem -> 8867006a.0 link Go_Daddy_Class_2_CA.pem -> f081611a.0 link Amazon_Root_CA_3.pem -> 8cb5ee0f.0 link Starfield_Root_Certificate_Authority_-_G2.pem -> 4bfab552.0 link QuoVadis_Root_CA_3.pem -> 76faf6c0.0 link GDCA_TrustAUTH_R5_ROOT.pem -> 0f6fa695.0 link OISTE_WISeKey_Global_Root_GA_CA.pem -> b1b8a7f3.0 link Entrust.net_Premium_2048_Secure_Server_CA.pem -> aee5f10d.0 link DigiCert_Global_Root_G3.pem -> dd8e9d41.0 link Cybertrust_Global_Root.pem -> 76cb8f92.0 link SSL.com_EV_Root_Certification_Authority_RSA_R2.pem -> 06dc52d5.0 link SSL.com_EV_Root_Certification_Authority_ECC.pem -> f0c70a8d.0 link DigiCert_Global_Root_G2.pem -> 607986c7.0 link Certplus_Class_2_Primary_CA.pem -> f060240e.0 link stunnel.pem -> eaf99eea.0 link GlobalSign_ECC_Root_CA_-_R5.pem -> 1d3472b9.0 link GlobalSign_Root_CA_-_R2.pem -> 4a6481c9.0 link Secure_Global_CA.pem -> b66938e9.0 link TrustCor_RootCert_CA-1.pem -> 5d3033c5.0 link OISTE_WISeKey_Global_Root_GB_CA.pem -> e73d606e.0 link DigiCert_High_Assurance_EV_Root_CA.pem -> 244b5494.0 link COMODO_RSA_Certification_Authority.pem -> d6325660.0 link USERTrust_RSA_Certification_Authority.pem -> fc5a8f99.0 link CFCA_EV_ROOT.pem -> 0b1b94ef.0 link OISTE_WISeKey_Global_Root_GC_CA.pem -> 773e07ad.0 link Entrust_Root_Certification_Authority_-_EC1.pem -> 106f3e4d.0 link D-TRUST_Root_Class_3_CA_2_2009.pem -> c28a8a30.0 link SwissSign_Gold_CA_-_G2.pem -> 4f316efb.0 link thawte_Primary_Root_CA.pem -> 2e4eed3c.0 link Verisign_Class_3_Public_Primary_Certification_Authority_-_G3.pem -> c0ff1f52.0 link Atos_TrustedRoot_2011.pem -> e36a6752.0 link Deutsche_Telekom_Root_CA_2.pem -> 812e17de.0 link EC-ACC.pem -> 349f2832.0 link TWCA_Root_Certification_Authority.pem ->
Bug#922062: ca-certificates package post-installation script subprocess returned error exit status 1
Mystery solved: Somebody (or something) placed a private key in a file called privkey.pem and stored it in /etc/ssl/certs. This caused openssl rehash to silently exit with error code 1, thus causing the whole postinst script to fail. After cleaning out the offending file, the package installed without any problems. - Michel
Bug#922062: ca-certificates package post-installation script subprocess returned error exit status 1
Package: ca-certificates Version: 20190110 Severity: normal Dear Maintainer, Installing the latest version of the package fails: Setting up ca-certificates (20190110) ... Updating certificates in /etc/ssl/certs... dpkg: error processing package ca-certificates (--configure): installed ca-certificates package post-installation script subprocess returned error exit status 1 -- It's not quite clear why (error message doesn't point to a particular issue). I'm thinking it's something on this box causing the postinst script to error out, but have no leads as to what. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.70 ii openssl1.1.1a-1 ca-certificates recommends no packages. ca-certificates suggests no packages. -- debconf information: * ca-certificates/enable_crts: GLC.crt, mozilla/ACCVRAIZ1.crt, mozilla/AC_RAIZ_FNMT-RCM.crt, mozilla/Actalis_Authentication_Root_CA.crt, mozilla/AddTrust_External_Root.crt, mozilla/AffirmTrust_Commercial.crt, mozilla/AffirmTrust_Networking.crt, mozilla/AffirmTrust_Premium.crt, mozilla/AffirmTrust_Premium_ECC.crt, mozilla/Amazon_Root_CA_1.crt, mozilla/Amazon_Root_CA_2.crt, mozilla/Amazon_Root_CA_3.crt, mozilla/Amazon_Root_CA_4.crt, mozilla/Atos_TrustedRoot_2011.crt, mozilla/Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.crt, mozilla/Baltimore_CyberTrust_Root.crt, mozilla/Buypass_Class_2_Root_CA.crt, mozilla/Buypass_Class_3_Root_CA.crt, mozilla/CA_Disig_Root_R2.crt, mozilla/Certigna.crt, mozilla/Certinomis_-_Root_CA.crt, mozilla/Certplus_Class_2_Primary_CA.crt, mozilla/certSIGN_ROOT_CA.crt, mozilla/Certum_Trusted_Network_CA_2.crt, mozilla/Certum_Trusted_Network_CA.crt, mozilla/CFCA_EV_ROOT.crt, mozilla/Chambers_of_Commerce_Root_-_2008.crt, mozilla/Comodo_AAA_Services_root.crt, mozilla/COMODO_Certification_Authority.crt, mozilla/COMODO_ECC_Certification_Authority.crt, mozilla/COMODO_RSA_Certification_Authority.crt, mozilla/Cybertrust_Global_Root.crt, mozilla/Deutsche_Telekom_Root_CA_2.crt, mozilla/DigiCert_Assured_ID_Root_CA.crt, mozilla/DigiCert_Assured_ID_Root_G2.crt, mozilla/DigiCert_Assured_ID_Root_G3.crt, mozilla/DigiCert_Global_Root_CA.crt, mozilla/DigiCert_Global_Root_G2.crt, mozilla/DigiCert_Global_Root_G3.crt, mozilla/DigiCert_High_Assurance_EV_Root_CA.crt, mozilla/DigiCert_Trusted_Root_G4.crt, mozilla/DST_Root_CA_X3.crt, mozilla/D-TRUST_Root_Class_3_CA_2_2009.crt, mozilla/D-TRUST_Root_Class_3_CA_2_EV_2009.crt, mozilla/EC-ACC.crt, mozilla/EE_Certification_Centre_Root_CA.crt, mozilla/Entrust.net_Premium_2048_Secure_Server_CA.crt, mozilla/Entrust_Root_Certification_Authority.crt, mozilla/Entrust_Root_Certification_Authority_-_EC1.crt, mozilla/Entrust_Root_Certification_Authority_-_G2.crt, mozilla/ePKI_Root_Certification_Authority.crt, mozilla/E-Tugra_Certification_Authority.crt, mozilla/GDCA_TrustAUTH_R5_ROOT.crt, mozilla/GeoTrust_Global_CA.crt, mozilla/GeoTrust_Primary_Certification_Authority.crt, mozilla/GeoTrust_Primary_Certification_Authority_-_G2.crt, mozilla/GeoTrust_Primary_Certification_Authority_-_G3.crt, mozilla/GeoTrust_Universal_CA_2.crt, mozilla/GeoTrust_Universal_CA.crt, mozilla/Global_Chambersign_Root_-_2008.crt, mozilla/GlobalSign_ECC_Root_CA_-_R4.crt, mozilla/GlobalSign_ECC_Root_CA_-_R5.crt, mozilla/GlobalSign_Root_CA.crt, mozilla/GlobalSign_Root_CA_-_R2.crt, mozilla/GlobalSign_Root_CA_-_R3.crt, mozilla/GlobalSign_Root_CA_-_R6.crt, mozilla/Go_Daddy_Class_2_CA.crt, mozilla/Go_Daddy_Root_Certificate_Authority_-_G2.crt, mozilla/Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015.crt, mozilla/Hellenic_Academic_and_Research_Institutions_RootCA_2011.crt, mozilla/Hellenic_Academic_and_Research_Institutions_RootCA_2015.crt, mozilla/Hongkong_Post_Root_CA_1.crt, mozilla/IdenTrust_Commercial_Root_CA_1.crt, mozilla/IdenTrust_Public_Sector_Root_CA_1.crt, mozilla/ISRG_Root_X1.crt, mozilla/Izenpe.com.crt, mozilla/LuxTrust_Global_Root_2.crt, mozilla/Microsec_e-Szigno_Root_CA_2009.crt, mozilla/NetLock_Arany_=Class_Gold=_Főtanúsítvány.crt, mozilla/Network_Solutions_Certificate_Authority.crt, mozilla/OISTE_WISeKey_Global_Root_GA_CA.crt, mozilla/OISTE_WISeKey_Global_Root_GB_CA.crt, mozilla/OISTE_WISeKey_Global_Root_GC_CA.crt, mozilla/QuoVadis_Root_CA_1_G3.crt, mozilla/QuoVadis_Root_CA_2.crt, mozilla/QuoVadis_Root_CA_2_G3.crt, mozilla/QuoVadis_Root_CA_3.crt, mozilla/QuoVadis_Root_CA_3_G3.crt, mozilla/QuoVadis_Root_CA.crt,
Bug#881494: chromium: chormium crash on startup
Package: chromium Version: 64.0.3282.119-2 Followup-For: Bug #881494 Dear Maintainer, Alas, this bug persists. When started with the Media Router Extension enabled, Chromium immediately crashes: [19661:19661:0212/180641.943907:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) [19661:19661:0212/180643.025328:ERROR:account_tracker.cc(278)] OnGetTokenFailure: Invalid credentials. [19661:19661:0212/180643.025372:ERROR:account_tracker.cc(278)] OnGetTokenFailure: Invalid credentials. [19661:19661:0212/180643.781786:ERROR:display_info_provider_aura.cc(31)] Not implemented reached in virtual void extensions::DisplayInfoProviderAura::UpdateDisplayUnitInfoForPla tform(const display::Display&, extensions::api::system_display::DisplayUnitInfo*) Received signal 11 SEGV_MAPERR 0010 #0 0x55f460767dee #1 0x55f45efe6ec8 #2 0x55f4607681a7 #3 0x7f2d35731160 #4 0x55f45fa6d895 #5 0x55f45fa6e817 #6 0x55f45fa6ee82 #7 0x55f45fa6f00f #8 0x55f4607cfbac #9 0x55f4607691ff #10 0x55f46078886e #11 0x55f46078969c #12 0x55f4607897fa #13 0x55f46078b1ca #14 0x55f4607b210a #15 0x55f4607d4b3f #16 0x55f4607cfaa1 #17 0x7f2d3572651a start_thread #18 0x7f2d29ea337f clone r8: 01b7f9118cd0 r9: 0004 r10: 55f463940650 r11: 7f2d29f309e0 r12: 7f2cf6f8bf80 r13: 0008 r14: r15: 7f2cf6f8c190 di: si: 7f2cf6f8bf80 bp: 7f2cf6f8bf40 bx: 7f2cf6f8bfa0 dx: 0001 ax: 01b7f8be8e70 cx: sp: 7f2cf6f8bf20 ip: 55f45fa6d895 efl: 00010206 cgf: 002b0033 erf: 0004 trp: 000e msk: cr2: 0010 [end of stack trace] Calling _exit(1). Core file will not be generated. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (500, 'oldoldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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 chromium depends on: ii chromium-common 64.0.3282.119-2 ii libasound2 1.1.3-5 ii libatk-bridge2.0-0 2.26.1-1 ii libatk1.0-0 2.26.1-3 ii libavcodec57 10:3.2.2-dmo1 ii libavformat57 10:3.2.2-dmo1 ii libavutil55 10:3.2.2-dmo1 ii libc6 2.26-2 ii libcairo2 1.15.10-1 ii libcups2 2.2.6-4 ii libdbus-1-3 1.12.2-1 ii libevent-2.1-6 2.1.8-stable-4 ii libexpat1 2.2.5-3 ii libflac8 1.3.2-1 ii libfontconfig1 2.12.6-0.1 ii libfreetype6 2.8.1-1 ii libgcc1 1:7.2.0-19 ii libgdk-pixbuf2.0-0 2.36.11-1 ii libglib2.0-0 2.54.3-2 ii libgtk-3-0 3.22.26-2 ii libharfbuzz0b 1.7.2-1 ii libicu57 57.1-8 ii libjpeg62-turbo 1:1.5.2-2+b1 ii liblcms2-2 2.9-1 ii libminizip1 1.1-8+b1 ii libnspr4 2:4.18-1 ii libnss3 2:3.35-2 ii libopus0 1.2.1-1 ii libpango-1.0-0 1.40.14-1 ii libpangocairo-1.0-0 1.40.14-1 ii libpng16-16 1.6.34-1 ii libpulse0 11.1-4 ii libre2-3 20170101+dfsg-1 ii libsnappy1v5 1.1.7-1 ii libstdc++6 7.2.0-19 ii libvpx4 1.6.1-3 ii libwebp6 0.6.0-4 ii libwebpdemux2 0.6.0-4 ii libwebpmux3 0.6.0-4 ii libx11-6 2:1.6.4-3 ii libx11-xcb1 2:1.6.4-3 ii libxcb1 1.12-1 ii libxcomposite1 1:0.4.4-2 ii libxcursor1 1:1.1.15-1 ii libxdamage1 1:1.1.4-3 ii libxext6 2:1.3.3-1+b2 ii libxfixes3 1:5.0.3-1 ii libxi6 2:1.7.9-1 ii libxml2 2.9.4+dfsg1-6.1 ii libxrandr2 2:1.5.1-1 ii libxrender1 1:0.9.10-1 ii libxslt1.1 1.1.29-5 ii libxss1 1:1.2.2-1+b2 ii libxtst6 2:1.2.3-1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages chromium recommends: ii fonts-liberation 1:1.07.4-5 Versions of packages chromium suggests: pn chromium-driver pn chromium-l10n pn chromium-shell pn chromium-widevine -- no debconf information
Bug#863281: Fixed upstream
FYI: As per https://support.zabbix.com/browse/ZBX-11042, this bug was fixed upstream in svn://svn.zabbix.com/branches/dev/ZBX-11042 revision r71721. - Michel
Bug#863281: zabbix: Does not support AUTH LOGIN for SMTP
Source: zabbix Severity: wishlist Tags: patch upstream Dear Maintainer, Zabbix only supports AUTH PLAIN when talking SMTP. This prevents it from being used with SMTP MTAs that require AUTH LOGIN (like Exchange Online / Office 365). (https://support.zabbix.com/browse/ZBXNEXT-3367) Attached is a patch that allows users to select AUTH LOGIN when configuring the email media type. -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldoldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Description: Add AUTH LOGIN support for SMTP (email media types) Enable users to select AUTH LOGIN as authentication method when configuring email media types. . zabbix (1:3.0.7+dfsg-2) unstable; urgency=medium . Author: Michel Meyers <deb...@tcnnet.com> Bug-Debian: https://bugs.debian.org/857287 Bug: https://support.zabbix.com/browse/ZBXNEXT-3367 --- Last-Update: 2017-05-24 --- zabbix-3.0.7+dfsg.orig/frontends/php/app/controllers/CControllerMediatypeCreate.php +++ zabbix-3.0.7+dfsg/frontends/php/app/controllers/CControllerMediatypeCreate.php @@ -32,7 +32,7 @@ class CControllerMediatypeCreate extends 'smtp_security' => 'db media_type.smtp_security|in '.SMTP_CONNECTION_SECURITY_NONE.','.SMTP_CONNECTION_SECURITY_STARTTLS.','.SMTP_CONNECTION_SECURITY_SSL_TLS, 'smtp_verify_peer' => 'db media_type.smtp_verify_peer|in 0,1', 'smtp_verify_host' => 'db media_type.smtp_verify_host|in 0,1', - 'smtp_authentication' =>'db media_type.smtp_authentication|in '.SMTP_AUTHENTICATION_NONE.','.SMTP_AUTHENTICATION_NORMAL, + 'smtp_authentication' =>'db media_type.smtp_authentication|in '.SMTP_AUTHENTICATION_NONE.','.SMTP_AUTHENTICATION_NORMAL.','.SMTP_AUTHENTICATION_NORMAL_LOGIN, 'exec_path' => 'db media_type.exec_path', 'eztext_limit' => 'in '.EZ_TEXTING_LIMIT_USA.','.EZ_TEXTING_LIMIT_CANADA, 'exec_params' =>'array media_type.exec_params', --- zabbix-3.0.7+dfsg.orig/frontends/php/app/controllers/CControllerMediatypeEdit.php +++ zabbix-3.0.7+dfsg/frontends/php/app/controllers/CControllerMediatypeEdit.php @@ -39,7 +39,7 @@ class CControllerMediatypeEdit extends C 'smtp_security' => 'db media_type.smtp_security|in '.SMTP_CONNECTION_SECURITY_NONE.','.SMTP_CONNECTION_SECURITY_STARTTLS.','.SMTP_CONNECTION_SECURITY_SSL_TLS, 'smtp_verify_peer' => 'db media_type.smtp_verify_peer|in 0,1', 'smtp_verify_host' => 'db media_type.smtp_verify_host|in 0,1', - 'smtp_authentication' =>'db media_type.smtp_authentication|in '.SMTP_AUTHENTICATION_NONE.','.SMTP_AUTHENTICATION_NORMAL, + 'smtp_authentication' =>'db media_type.smtp_authentication|in '.SMTP_AUTHENTICATION_NONE.','.SMTP_AUTHENTICATION_NORMAL.','.SMTP_AUTHENTICATION_NORMAL_LOGIN, 'exec_path' => 'db media_type.exec_path', 'eztext_limit' => 'in '.EZ_TEXTING_LIMIT_USA.','.EZ_TEXTING_LIMIT_CANADA, 'exec_params' =>'array media_type.exec_params', --- zabbix-3.0.7+dfsg.orig/frontends/php/app/controllers/CControllerMediatypeUpdate.php +++ zabbix-3.0.7+dfsg/frontends/php/app/controllers/CControllerMediatypeUpdate.php @@ -33,7 +33,7 @@ class CControllerMediatypeUpdate extends 'smtp_security' => 'db media_type.smtp_security|in '.SMTP_CONNECTION_SECURITY_NONE.','.SMTP_CONNECTION_SECURITY_STARTTLS.','.SMTP_CONNECTION_SECURITY_SSL_TLS, 'smtp_verify_peer' => 'db media_type.smtp_verify_peer|in 0,1', 'smtp_verify_host' => 'db media_type.smtp_verify_host|in 0,1', - 'smtp_authentication' =>'db media_type.smtp_authentication|in '.SMTP_AUTHENTICATION_NONE.','.SMTP_AUTHENTICATION_NORMAL, + 'smtp_authentication' =>'db media_type.smtp_authentication|in '.SMTP_AUTHENTICATION_NONE.','.SMTP_AUTHENTICATION_NORMAL.','.SMTP_AUTHENTICATION_NORMAL_LOGIN, 'exec_path' => 'db media_type.exec_path', 'eztext_limit' => 'in '.EZ_TEXTING_LIMIT_USA.','.EZ_TEXTING_LIMIT_CAN
Bug#850258: glances: calling home?
Can't comment on the others but li1176-20.members.linode.com runs an SSL certificate with "ipv4.jsonip.com" in the CN, so something is using jsonip.com to pull a JSON object with your external IPv4 IP in it. - Michel
Bug#838640: deluge: New version 1.3.13 has been released
Package: deluge Version: 1.3.12-1 Severity: wishlist Dear Maintainer, 1.3.13 has been released. It would be nice if you could package it. http://dev.deluge-torrent.org/wiki/ReleaseNotes/1.3.13 Thanks for your hard work. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldoldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.5.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages deluge depends on: ii deluge-gtk 1.3.12-1 ii python-libtorrent 1.1.0-3 pn python:any deluge recommends no packages. deluge suggests no packages. -- no debconf information
Bug#823240: vlan: Does not work with interfaces named eno*
Subject: vlan: Does not work with interfaces named eno* Package: vlan Version: 1.9-3.2 Severity: wishlist Dear Maintainer, I recently ran into some VLAN issues on a new server and found that it names all its interfaces eno1, The following vlan scripts appear to only take into account eth, bond and wlan interfaces: /etc/network/if-pre-up.d/vlan /etc/network/if-post-down.d/vlan It would be nice if you could also make them handle eno interfaces. Thanks for your work. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.4.0-1-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 vlan depends on: ii iproute2 4.3.0-1+b1 ii libc6 2.22-7 vlan recommends no packages. vlan suggests no packages. -- no debconf information
Bug#818389: iaxmodem: New upstream available 1.3.0
Package: iaxmodem Version: 1.2.0~dfsg-2 Severity: wishlist Tags: upstream Dear Maintainer, A new upstream version of this software appears to be available: https://sourceforge.net/projects/iaxmodem/files/iaxmodem/iaxmodem-1.3.0.tar.gz/download Thanks for your work! -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldoldstable') Architecture: i386 (i686) Kernel: Linux 4.3.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages iaxmodem depends on: ii libc6 2.21-9 iaxmodem recommends no packages. iaxmodem suggests no packages. -- no debconf information
Bug#813585: Confirmed
I can confirm this to be an issue with 2.5+dfsg-4+b1 and also confirm
that re-compiling it with the upstream patch makes it work correctly.
--- qemu-2.5+dfsg.orig/block.c
+++ qemu-2.5+dfsg/block.c
@@ -2028,7 +2028,7 @@ static void change_parent_backing_link(B
}
if (from->blk) {
blk_set_bs(from->blk, to);
-if (!to->device_list.tqe_prev) {
+if (!to->device_list.tqe_prev || !*to->device_list.tqe_prev) {
QTAILQ_INSERT_BEFORE(from, to, device_list);
}
QTAILQ_REMOVE(_states, from, device_list);
- Michel
Bug#815319:
Got the same issue here. Applying the suggestions from this bug helped: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813339 (Setting INTERFACESv4 to an actual interface rather than leaving it empty) - Michel
Bug#805444: multipath-tools: Installation fails with "Unit blk-availability.service failed to load"
On 2015-11-18 10:51, Ritesh Raj Sarraf wrote: > Please share the content of multipath-tools.service file. > > My guess is that you are using the .service file from a different > source. Here's the content: [Unit] Description=Device-Mapper Multipath Device Controller Requires=blk-availability.service Before=iscsi.service iscsid.service lvm2-activation-early.service Before=local-fs-pre.target After=multipathd.socket DefaultDependencies=no Wants=local-fs-pre.target multipathd.socket Conflicts=shutdown.target [Service] Type=notify NotifyAccess=main LimitCORE=infinity ExecStartPre=/sbin/modprobe dm-multipath ExecStart=/sbin/multipathd -d -s ExecReload=/sbin/multipathd reconfigure [Install] WantedBy=sysinit.target Also=multipathd.socket Alias=multipath-tools.service This appears to match the content of the respective file from the archive here: https://packages.debian.org/stretch/amd64/multipath-tools/download
Bug#805444: multipath-tools: Installation fails with "Unit blk-availability.service failed to load"
Package: multipath-tools
Version: 0.5.0+git1.656f8865-1
Severity: important
Dear Maintainer,
dpkg fails while upgrading multipath-tools. The errors look like this:
Installing new version of config file /etc/init.d/multipath-tools ...
Failed to start multipath-tools.service: Unit blk-availability.service
failed to load: No such file or directory.
invoke-rc.d: initscript multipath-tools, action "start" failed.
dpkg: error processing package multipath-tools (--configure):
subprocess installed post-installation script returned error exit status 6
I've tried to look for a package containing the blk-availability.service
file but couldn't find one in any Debian release branch.
-- Package-specific info:
Contents of /etc/multipath.conf:
defaults {
polling_interval5
path_selector"round-robin 0"
path_grouping_policymultibus
path_checkerdirectio
rr_min_io 10
rr_min_io_rq10
rr_weight priorities
failbackimmediate
no_path_retry queue
user_friendly_names yes
}
blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^hd[a-z][[0-9]*]"
devnode "^vd[a-z]"
devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*]"
device {
vendor DEC.*
product MSA[15]00
}
}
multipaths {
multipath {
wwid 36001405f4600cb3d523ad356adb297de
alias rsphotoserver_lun1
path_selector "round-robin 0"
}
multipath {
wwid 36001405ddcb754cd055dd38b8d80a6d2
alias server1root_vgstorage
path_selector "round-robin 0"
}
multipath {
wwid 360014051385e8a4d155cd3f54dac97da
alias vboxserver2
path_selector "round-robin 0"
}
}
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-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 multipath-tools depends on:
ii init-system-helpers 1.24
ii initscripts 2.88dsf-59.2
ii kpartx 0.5.0+git1.656f8865-1
ii libaio1 0.3.110-2
ii libc62.19-22
ii libdevmapper1.02.1 2:1.02.110-1
ii libgcc1 1:5.2.1-23
ii libreadline6 6.3-8+b3
ii libsystemd0 227-2
ii libudev1 227-2
ii lsb-base 9.20150917
ii sg3-utils-udev 1.41-1
ii udev 227-2
multipath-tools recommends no packages.
Versions of packages multipath-tools suggests:
pn multipath-tools-boot
-- no debconf information
Bug#798237: Same issue, compile with NSUPDATE fails
Same issue here. The 4.3.3 release seems to be missing DDNS update functionality completely. Trying to undo the disable-nsupdate.patch and manually compiling the package fails too: --- ../omapip/libomapi.a(isclib.o): In function `dhcp_dns_client_setservers': /root/swdown/dhcp/isc-dhcp-4.3.3/omapip/isclib.c:51: undefined reference to `irs_resconf_load' /root/swdown/dhcp/isc-dhcp-4.3.3/omapip/isclib.c:58: undefined reference to `irs_resconf_getnameservers' collect2: error: ld returned 1 exit status distcc[21884] ERROR: compile (null) on localhost failed Makefile:439: recipe for target 'dhclient' failed make[4]: *** [dhclient] Error 1 make[4]: Leaving directory '/root/swdown/dhcp/isc-dhcp-4.3.3/client' Makefile:580: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/root/swdown/dhcp/isc-dhcp-4.3.3/client' Makefile:426: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/root/swdown/dhcp/isc-dhcp-4.3.3' debian/rules:46: recipe for target 'override_dh_auto_build' failed make[1]: *** [override_dh_auto_build] Error 2 make[1]: Leaving directory '/root/swdown/dhcp/isc-dhcp-4.3.3' debian/rules:41: recipe for target 'build' failed make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 --- Downgraded to 4.3.2 for now.
Bug#732899: Add MariaDB as an alternative dependency
libmysqlclient18 does not conflict with mariadb-client/server (I does not require mysql-client and is satisfied by having just mysql-common). Would replacing the mysql-client dependency with libmysqlclient18 work? - Michel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#760515: ocsinventory-server: Version 2.1.2 of the server is available.
Source: ocsinventory-server Version: 2.0.5-1.1 Severity: wishlist Dear Maintainer, Version 2.1.2 is available upstream. It would be awesome if you could update this package. Thanks for all your work. - Michel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759022: ifupdown: Fails to bring up vlan interfaces
Package: ifupdown Version: 0.7.48.1 Severity: normal Dear Maintainer, I recently noticed that my system does not bring up its VLAN interfaces correctly on boot any more (I have to manually ifconfig up them and add the default route/extra routes). If I try to manually bring up a VLAN interface after boot, I get this: root@server:~# ifup eth0.1 Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config RTNETLINK answers: File exists Failed to bring up eth0.1. These are the active routes at that point: Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 10.8.0.010.8.0.2255.255.255.0 UG0 00 tun0 10.8.0.20.0.0.0 255.255.255.255 UH0 00 tun0 10.32.0.0 10.205.0.1 255.240.0.0 UG0 00 eth1 10.100.100.00.0.0.0 255.255.255.0 U 0 00 eth2 10.101.101.00.0.0.0 255.255.255.0 U 0 00 eth3 10.205.0.0 0.0.0.0 255.255.255.248 U 0 00 eth1 And this is the configuration: # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8) # The loopback interface # automatically added when upgrading auto lo iface lo inet loopback # automatically added when upgrading auto eth0 #tried with the above on and commented out auto eth1 auto eth2 auto eth3 iface eth0 inet static address 0.0.0.0 #tried with and without the 2 lines above, no avail #iface eth0 inet static # address 10.78.78.2 # netmask 255.255.255.0 # gateway 10.78.78.1 # up route add -net 10.77.77.0 netmask 255.255.255.0 gw 10.78.78.11 # down route del -net 10.77.77.0 netmask 255.255.255.0 gw 10.78.78.11 # # mtu 1492 # mtu 9000 iface eth1 inet static address 10.205.0.4 netmask 255.255.255.248 up route add -net 10.32.0.0 netmask 255.240.0.0 gw 10.205.0.1 down route del -net 10.32.0.0 netmask 255.240.0.0 gw 10.205.0.1 iface eth2 inet static address 10.100.100.2 netmask 255.255.255.0 mtu 9000 iface eth3 inet static address 10.101.101.2 netmask 255.255.255.0 mtu 9000 auto eth0.1 iface eth0.1 inet static address 10.78.78.2 netmask 255.255.255.0 gateway 10.78.78.1 vlan-raw-device eth0 up route add -net 10.77.77.0 netmask 255.255.255.0 gw 10.78.78.11 down route del -net 10.77.77.0 netmask 255.255.255.0 gw 10.78.78.11 mtu 9000 auto eth0.4 iface eth0.4 inet static address 10.80.80.2 netmask 255.255.255.0 vlan-raw-device eth0 Is there a config error that I am overlooking? - Michel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-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 Versions of packages ifupdown depends on: ii adduser 3.113+nmu3 ii initscripts 2.88dsf-53.3 ii iproute 1:3.16.0-1 ii iproute2 3.16.0-1 ii libc62.19-9 ii lsb-base 4.1+Debian13 Versions of packages ifupdown recommends: ii pump [dhcp-client] 0.8.24-7 Versions of packages ifupdown suggests: ii net-tools 1.60-26 ii ppp2.4.6-2 pn rdnssd none -- debconf information: ifupdown/convert-interfaces: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747849: python-gdata: Getting contacts fails after Google forces SSL
Package: python-gdata
Version: 2.0.18+dfsg-1
Severity: important
Tags: patch
Dear Maintainer,
Trying to access contacts in python, this error now pops up:
Traceback (most recent call last):
File /usr/lib/python2.7/dist-packages/gdata/contacts/service.py, line 104,
in GetContactsFeed
return self.Get(uri, converter=gdata.contacts.ContactsFeedFromString)
File /usr/lib/python2.7/dist-packages/gdata/service.py, line 1107, in Get
'reason': server_response.reason, 'body': result_body}
gdata.service.RequestError: {'status': 301, 'body':
'HTML\nHEAD\nTITLEMoved Permanently/TITLE\n/HEAD\nBODY
BGCOLOR=#FF TEXT=#00\nH1Moved Permanently/H1\nThe document has
moved A
HREF=https://www.google.com/m8/feeds/contacts/default/full?max-results=1000;here/A.\n/BODY\n/HTML\n',
'reason': 'Moved Permanently'}
The reason for that appears to be that Google is now forcing HTTPS and has
therefore placed a 301 redirect at the original URI, which the script doesn't
handle correctly.
(See upstream bug report here:
https://code.google.com/p/gdata-python-client/issues/detail?id=693 )
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable')
Architecture: i386 (i686)
Kernel: Linux 3.11-2-686-pae (SMP w/4 CPU cores)
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 python-gdata depends on:
ii python 2.7.5-5
ii python-crypto 2.6.1-4
python-gdata recommends no packages.
Versions of packages python-gdata suggests:
pn python-gdata-doc none
-- no debconf information
--- python-gdata-2.0.18+dfsg/src/gdata/service.py 2014-05-12 09:19:37.433594330 +0200
+++ python-gdata-2.0.18+dfsg/src/gdata/service.py 2014-05-12 09:20:07.814531042 +0200
@@ -1084,7 +1084,7 @@
return result_body
return entry
return feed
-elif server_response.status == 302:
+elif server_response.status == 302 or server_response.status == 301:
if redirects_remaining 0:
location = (server_response.getheader('Location')
or server_response.getheader('location'))
Bug#737517: stunnel4: Should block OpenSSL 1.0.1f (needs new build)
Package: stunnel4 Version: 3:4.53-1.1 Severity: important Dear Maintainer, After the upgrade to openssl 1.0.1f-1, stunnel4 no longer starts: Starting SSL tunnels: Clients allowed=32000 stunnel 4.53 on x86_64-pc-linux-gnu platform Compiled with OpenSSL 1.0.1e 11 Feb 2013 Running with OpenSSL 1.0.1f 6 Jan 2014 Update OpenSSL shared libraries or rebuild stunnel Threading:PTHREAD SSL:+ENGINE+OCSP Auth:LIBWRAP Sockets:POLL+IPv6 Reading configuration from file /etc/stunnel/elasticsearch.conf Failed to initialize compression method str_stats: 9 block(s), 179 data byte(s), 522 control byte(s) Fix: - Downgrade OpenSSL to 1.0.1e-2 - Rebuild stunnel with OpenSSL 1.0.1f-1 I've resolved the issue manually on my end, but please have a look and provide a new build if necessary. Thanks for your time and work! - Michel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (550, 'experimental'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.11-2-686-pae (SMP w/4 CPU cores) 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 stunnel4 depends on: ii adduser 3.113+nmu3 ii libc6 2.17-97 ii libssl1.0.0 1.0.1f-1 ii libwrap0 7.6.q-25 ii netbase 5.2 ii openssl 1.0.1f-1 ii perl-modules 5.18.2-2 ii zlib1g1:1.2.8.dfsg-1 stunnel4 recommends no packages. Versions of packages stunnel4 suggests: ii logcheck-database 1.3.16 -- Configuration Files: /etc/default/stunnel4 changed [not included] /etc/ppp/ip-down.d/0stunnel4 [Errno 13] Permission denied: u'/etc/ppp/ip-down.d/0stunnel4' /etc/ppp/ip-up.d/0stunnel4 [Errno 13] Permission denied: u'/etc/ppp/ip-up.d/0stunnel4' /etc/stunnel/stunnel.conf changed [not included] -- 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#717312: 'TypeError: daemonize() takes exactly 2 arguments (0 given)' while upgrading
Package: pymsnt Version: 0.11.3-5 Severity: grave Tags: patch Justification: renders package unusable While upgrading the pymsnt package, dpkg bails out in the pre-removal script: dpkg: error processing pymsnt_0.11.3-5.1_all.deb (--install): subprocess new pre-removal script returned error exit status 1 Starting MSN transport for Jabber: Traceback (most recent call last): File /usr/share/pymsnt/PyMSNt.py, line 14, in module main.main() File /usr/share/pymsnt/src/main.py, line 390, in main app = App() File /usr/share/pymsnt/src/main.py, line 331, in __init__ twistd.daemonize() TypeError: daemonize() takes exactly 2 arguments (0 given) invoke-rc.d: initscript pymsnt, action start failed. dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: pymsnt_0.11.3-5.1_all.deb The problem seems to be in line 331 of /usr/share/pymsnt/src/main.py: twistd.daemonize() Changing it to: twistd.daemonize(reactor, os) seems to make it start up. - Michel -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.9-1-686-pae (SMP w/4 CPU cores) 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 pymsnt depends on: ii adduser 3.113+nmu3 ii python 2.7.5-2 ii python-central 0.6.17 ii python-crypto 2.6-5 ii python-openssl 0.13-2+b1 ii python-twisted 13.0.0-1 Versions of packages pymsnt recommends: ii python-imaging 1.1.7-4 Versions of packages pymsnt suggests: ii ejabberd 2.1.10-5 -- Configuration Files: /etc/pymsnt.conf.xml changed [not included] -- no debconf information --- src/main.py 2013-07-19 10:02:34.0 +0200 +++ src/main.py 2013-07-19 10:02:50.0 +0200 @@ -328,7 +328,7 @@ # Daemonise the process and write the PID file if config.background and os.name == posix: - twistd.daemonize() + twistd.daemonize(reactor, os) if config.pid: self.writePID()
Bug#683727: closed by Dmitry Smirnov only...@member.fsf.org (Done: zabbix-server-mysql: Upgrade to 2.0 fails)
As we emphasised in NEWS, README and TODO files, the database upgrade procedure is now completely manual. I read the README.Debian (for the zabbix-server-mysql package) and it didn't mention it. The NEWS file however did, my bad. - Michel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683727: zabbix-server-mysql: Upgrade to 2.0 fails
Package: zabbix-server-mysql Version: 1:2.0.1+dfsg-1 Severity: grave Justification: renders package unusable Hello, During the recent package upgrade, Zabbix-Server was upgraded from 1.8 to 2.0 which resulted in a load of problems, probably due to issues with the DB upgrade (the web interface is complaining about missing fields, graphs, data etc is missing, I'm currently running the /usr/share/zabbix-server-mysql/patch.sql.gz file against my database to see if that can fix it. - Michel -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.37-1-686-bigmem (SMP w/4 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 zabbix-server-mysql depends on: ii adduser 3.113+nmu3 ii debconf 1.5.45 ii fping 3.2-1 ii libc6 2.13-35 ii libcurl3-gnutls 7.26.0-1 ii libiksemel3 1.2-4 ii libldap-2.4-2 2.4.31-1 ii libmysqlclient18 5.5.25a-rel27.1-277.squeeze ii libopenipmi0 2.0.16-1.3 ii libsnmp15 5.4.3~dfsg-2.5 ii libssh2-1 1.4.2-1 ii lsb-base 4.1+Debian7 ii ucf 3.0025+nmu3 Versions of packages zabbix-server-mysql recommends: ii percona-server-server-5.5 [mysql-server] 5.5.25a-rel27.1-277.squeeze ii snmpd 5.4.3~dfsg-2.5 Versions of packages zabbix-server-mysql suggests: ii logrotate3.8.1-4 ii zabbix-frontend-php 1:2.0.1+dfsg-1 -- Configuration Files: /etc/default/zabbix-server changed [not included] -- debconf information: zabbix-server-mysql/password-confirm: (password omitted) zabbix-server-mysql/mysql/admin-pass: (password omitted) zabbix-server-mysql/mysql/app-pass: (password omitted) zabbix-server-mysql/app-password-confirm: (password omitted) zabbix-server-mysql/upgrade-backup: true zabbix-server-mysql/import-oldsettings: zabbix-server-mysql/remote/host: zabbix-server-mysql/dbconfig-remove: zabbix-server-mysql/internal/skip-preseed: false zabbix-server-mysql/remove-error: abort * zabbix-server-mysql/server: zabbix-server-mysql/passwords-do-not-match: zabbix-server-mysql/missing-db-package-error: abort zabbix-server-mysql/db/dbname: zabbix zabbix-server-mysql/remote/newhost: * zabbix-server-mysql/dbconfig-install: true * zabbix-server-mysql/dbconfig-upgrade: true zabbix-server-mysql/mysql/admin-user: root zabbix-server-mysql/remote/port: zabbix-server-mysql/db/app-user: zabbix zabbix-server-mysql/database-type: mysql zabbix-server-mysql/purge: false zabbix-server-mysql/internal/reconfiguring: false zabbix-server-mysql/mysql/method: unix socket * zabbix-server-mysql/upgrade-error: retry (skip questions) zabbix-server-mysql/dbconfig-reinstall: false zabbix-server-mysql/install-error: retry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648946: chown: invalid user: `zabbix' in zabbix-server-mysql.postinst
Package: zabbix-server-mysql Followup-For: Bug #683727 Update: Running the patch.sql.gz script manually (with -f as it does give some errors) appears to have brought my Zabbix installation back to life. Not sure if the package upgrade wass supposed to do that and skipped it for some reason, or if the schema upgrade was forgotten entirely. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#683727: (no subject)
Update: Running the patch.sql.gz script manually (with -f as it does give some errors) appears to have brought my Zabbix installation back to life. Not sure if the package upgrade wass supposed to do that and skipped it for some reason, or if the schema upgrade was forgotten entirely. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674157: roundcube: Default language should not be Arabic
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/05/2012 21:17, Vincent Bernat wrote: OoO Vers la fin de l'après-midi du mercredi 23 mai 2012, vers 16:19, Michel Meyers stel...@tcnnet.com disait : From: $rcmail_config['language'] = 'ar_SA' To: $rcmail_config['language'] = NULL; The default is en_US. I think you get ar_SA because you set this through debconf. What do you get with: debconf-show roundcube-core | grep lang ? # debconf-show roundcube-core | grep lang roundcube/language: ar_SA I never set this anywhere though. This box was installed via debootstrap so maybe the root cause stems from there? I have installed it in a debootstrapped environment, I got no debconf question and I got en_US by default: root@neo:/# debconf-show roundcube-core | grep lang roundcube/language: en_US (It is a Squeeze debootstrap). How odd. Mine's squeeze (6.0.5) too. While reading up on how to change the language default, most documentation refers to dpkg-reconfigure locales but on my system, locales wasn't even installed. Maybe that's the source of the problem? I submitted the Debian bug after seeing this bug report for EHCP/Ubuntu, which I suppose uses the same codebase: https://bugs.launchpad.net/ehcp/+bug/800503 - - Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (MingW32) iEYEARECAAYFAk+95nIACgkQ2Vs+MkscAyU/pwCfcujKpkipld2fSU/9Rgg8X6KM UIcAoK2pIFyG7e7tNiQGaS+ypcHkHOwY =6N7B -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674157: roundcube: Default language should not be Arabic
Package: roundcube Version: 0.3.1-6 Severity: normal Dear Maintainer, Please change line 168 in /etc/roundcube/main.inc.php From: $rcmail_config['language'] = 'ar_SA' To: $rcmail_config['language'] = NULL; Thanks in advance, Michel -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674157: roundcube: Default language should not be Arabic
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/05/2012 15:25, Vincent Bernat wrote: Le 23.05.2012 14:22, Michel Meyers a écrit : Please change line 168 in /etc/roundcube/main.inc.php From: $rcmail_config['language'] = 'ar_SA' To: $rcmail_config['language'] = NULL; The default is en_US. I think you get ar_SA because you set this through debconf. What do you get with: debconf-show roundcube-core | grep lang ? # debconf-show roundcube-core | grep lang roundcube/language: ar_SA I never set this anywhere though. This box was installed via debootstrap so maybe the root cause stems from there? - - Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (MingW32) iEYEARECAAYFAk+88eoACgkQ2Vs+MkscAyXZTQCg8c+I3RPwF6kcScUjIP3mnb2k IDMAnii7K7qr2CEWl6Yq4nJnh7rl+76n =avyJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#639817: Recommends and breaks libiodbc2 at the same time
Package: tdsodbc Version: 0.82-8 Severity: normal Installing tdsodbc results in libiodbc2 getting uninstalled (and KDE with it) -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582582: qsynth: No sound after upgrade to 0.3.5-1
Package: qsynth Version: 0.3.5-1 Severity: important After upgrading to 0.3.5-1 yesterday, I could not get any audio out of Qsynth today. I'm using alsa_seq as MIDI input and jack as output. Qsynth is receiving MIDI signals (green indicator on the engine tab is flashing) but apparently not outputting any audio. Downgrading to 0.3.4-3 makes it work again. Please let me know if there is any further information you need or any testing required. - Michel -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686-bigmem (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 qsynth depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libfluidsynth11.1.1-4Real-time MIDI software synthesize ii libgcc1 1:4.4.4-1 GCC support library ii libqtcore44:4.6.2-4 Qt 4 core module ii libqtgui4 4:4.6.2-4 Qt 4 GUI module ii libstdc++64.4.4-1The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-3 X11 client-side library Versions of packages qsynth recommends: ii fluid-soundfont-gm3.1-5 Fluid (R3) General MIDI SoundFont ii qjackctl 0.3.6-1User interface for controlling the qsynth 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#564029: zabbix-frontend-php: Scrolling in graphs stops working in 1.8
Subject: zabbix-frontend-php: Scrolling in graphs stops working in 1.8 Package: zabbix-frontend-php Version: 1:1.8-1 Severity: normal Starting with Zabbix 1.8, the scrolling does no longer work in graphs (at least when accessing graphs via 'latest data'). A look into my apache logs shows, that the web browser is trying to access these two files and getting a 404: /zabbix/js/effects.js /zabbix/js/dragdrop.js These are actually part of scriptaculous but for some reason they are not being accessed in /zabbix/js/scriptaculous/... To work around the issue I created these two symlinks in /usr/share/zabbix/js: dragdrop.js - scriptaculous/dragdrop.js effects.js - scriptaculous/effects.js - Michel -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686-bigmem (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551973: Similar issue
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
I've managed to reproduce the crash again, this time on another xml file.
Background: fusecompress bailed out again (no logging available of
that). Subsequently, the file
'HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk' has become
unreadable... fusecompress complains about 'Failed to restore LayerMap'
(see below). Realizing that the file was gone, I attempted to 'release'
it in Virtualbox (and recreate a new one). When I did so, fusecompress
bailed out again. Here's the ending part of what it spit out:
new CFile(..., HardDisks)
N (HardDisks), 0x1000 bytes
getattr name: HardDisks, m_IsCompressed: 0, m_fh.size: 0x0
Memory::getattr(0xb69017e0) m_FileSize: 0x0, m_FileSizeSet: 0
virtual Compress::~Compress(), HardDisks
new CFile(..., HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk)
C (HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk), raw/user
0x6f22cbdb/0x7aa8 bytes
getattr name: HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk,
m_IsCompressed: 1, m_fh.size: 0x7aa8
Memory::getattr(0xb5600610) m_FileSize: 0x0, m_FileSizeSet: 0
virtual Compress::~Compress(),
HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk
new CFile(..., HardDisks)
N (HardDisks), 0x1000 bytes
getattr name: HardDisks, m_IsCompressed: 0, m_fh.size: 0x0
Memory::getattr(0xb69017e0) m_FileSize: 0x0, m_FileSizeSet: 0
virtual Compress::~Compress(), HardDisks
new CFile(..., HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk)
C (HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk), raw/user
0x6f22cbdb/0x7aa8 bytes
FuseCompress::open 0xb69017e0 name:
HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk
File::open file 'HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk',
inode 1459196, m_refs: 1
void Compress::restoreLayerMap(): fd: 10
int Compress::open(const char*, int): Failed to restore LayerMap of file
'HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk'
File::release m_refs: 0
Compress::release m_refs: 0, m_IsCompressed: 0
virtual Compress::~Compress(),
HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk
new CFile(..., HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk)
C (HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk), raw/user
0x6f22cbdb/0x7aa8 bytes
FuseCompress::open 0xb69017e0 name:
HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk
File::open file 'HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk',
inode 1459196, m_refs: 1
void Compress::restoreLayerMap(): fd: 10
int Compress::open(const char*, int): Failed to restore LayerMap of file
'HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk'
File::release m_refs: 0
Compress::release m_refs: 0, m_IsCompressed: 0
virtual Compress::~Compress(),
HardDisks/{b6f34842-93b2-4918-907e-244d75a74578}.vmdk
new CFile(..., HardDisks)
N (HardDisks), 0x1000 bytes
getattr name: HardDisks, m_IsCompressed: 0, m_fh.size: 0x0
Memory::getattr(0xb69017e0) m_FileSize: 0x0, m_FileSizeSet: 0
virtual Compress::~Compress(), HardDisks
getattr name: Machines/XP3/XP3.xml, m_IsCompressed: 1, m_fh.size: 0x1ebc
Memory::getattr(0xb69016f8) m_FileSize: 0x1ebc, m_FileSizeSet: 1
FuseCompress::write 0xb69016f8 name: Machines/XP3/XP3.xml, size: 0xfa3,
offset: 0x0
Memory::write(Machines/XP3/XP3.xml) | m_FileSize: 0x1ebc, size: 0xfa3,
offset: 0x0
FuseCompress::write 0xb69016f8 name: Machines/XP3/XP3.xml, size: 0x5d,
offset: 0xfa3
Memory::write(Machines/XP3/XP3.xml) | m_FileSize: 0x1ebc, size: 0x5d,
offset: 0xfa3
FuseCompress::write 0xb69016f8 name: Machines/XP3/XP3.xml, size: 0xb34,
offset: 0x1000
Memory::write(Machines/XP3/XP3.xml) | m_FileSize: 0x1ebc, size: 0xb34,
offset: 0x1000
FuseCompress::truncate file Machines/XP3/XP3.xml, to size: 1b34
truncate name: Machines/XP3/XP3.xml, m_IsCompressed: 1, size: 1b34
void Compress::DefragmentFast()
offset: 0x0, coffset: 0x19, size: 0x1b34
length: 0x655
ASSERT off_t Compress::cleverCopy(int, off_t, int, LayerMap) (r ==
writeOffset)
Aborted
- - Michel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (MingW32)
iEYEARECAAYFAksBakgACgkQ2Vs+MkscAyUi6QCgnlbW9Wcvh8qVxYTevdBJXMmM
70EAn3SGcK4fSyznnX52ZMuLbUu9Nrg6
=M3Tb
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#551973: Similar issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2009-11-08 7:30, Ritesh Raj Sarraf wrote: Unfortunately, I haven't been able to reproduce the problem yet. I copied like 10G of data to a fusecompressed mount point and still couldn't reproduce it. This bug has been forwarded upstream so that the devs can provide any more information. Please feel free to provide additional information you find. Meanwhile I will try to do another upload, perhaps with the tip, to the experimental archive. Ritesh Hello, I can't currently access the problematic machine (enjoying some time off work) but for me the issue only happened for VirtualBox.xml, which is less than 100k in size. Moving the uncompressed file to the root directory worked around the issue. As soon as the fusecompress headers are added, fusecompress bails out when the VirtualBox UI is started. I'll be out of office until Friday, so I won't be able to provide any debug info or do any testing until then. - - Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) iEYEARECAAYFAkr2+OEACgkQ2Vs+MkscAyV4cQCdGlnkS6rdyo9KRy2TrEfQLpqD oAgAn1cucJTzlYbHQsu1E6RifcOljI5x =iLCS -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#554500: grub-pc doesn't work with metadata 1.0 md device
Package: grub-pc
Version: 1.97-1
Severity: normal
Not sure if this is documented anywhere (just spend a few hours on this and
Google didn't come up with anything) but grub-pc doesn't work with md devices
when they are using metadata 1.0. Even after doing insmod raid and insmod
mdraid, the devicesi simply don't show up. grub-install keeps comlaining that
'no mapping exists for' the mdX device.
I was just giving up on grub and trying to switch to LILO, which immediately
complained about the metadata version, so I tried recreating the device with
0.90 metadata in the superblock and sure enough, that made grub find it
correctly.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/vgraid-lvroot / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/md3 /boot ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
/dev/mapper/vgraid-lvraid /storage ext3 rw,noatime,errors=continue,data=ordered
0 0
/dev/mapper/vgraid-lvroot /var/spool/hylafax/etc ext3
rw,relatime,errors=remount-ro,data=ordered 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/device.map
(hd0) /dev/hda
(hd1) /dev/hdb
(hd2) /dev/sda
(hd3) /dev/sdb
(hd4) /dev/sdc
(hd5) /dev/sdd
(hd6) /dev/sde
(hd7) /dev/sdf
*** END /boot/grub/device.map
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set default=0
insmod lvm
insmod ext2
set root=(vgraid-lvroot)
search --no-floppy --fs-uuid --set fb85ee57-d8a7-489c-83e6-2a9d146616b9
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don't
# understand terminal_output
terminal gfxterm
fi
fi
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod raid
insmod mdraid
insmod ext2
set root=(md3)
search --no-floppy --fs-uuid --set b87bc61c-9b61-4b99-aa49-b12c79836ae7
insmod png
if background_image /grub/moreblue-orbit-grub.png ; then
set color_normal=black/black
set color_highlight=magenta/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
menuentry Debian GNU/Linux, with Linux 2.6.30-2-686 {
insmod raid
insmod mdraid
insmod ext2
set root=(md3)
search --no-floppy --fs-uuid --set b87bc61c-9b61-4b99-aa49-b12c79836ae7
linux /vmlinuz-2.6.30-2-686 root=/dev/mapper/vgraid-lvroot ro
initrd /initrd.img-2.6.30-2-686
}
menuentry Debian GNU/Linux, with Linux 2.6.30-2-686 (recovery mode) {
insmod raid
insmod mdraid
insmod ext2
set root=(md3)
search --no-floppy --fs-uuid --set b87bc61c-9b61-4b99-aa49-b12c79836ae7
linux /vmlinuz-2.6.30-2-686 root=/dev/mapper/vgraid-lvroot ro single
initrd /initrd.img-2.6.30-2-686
}
menuentry Debian GNU/Linux, with Linux 2.6.30-1-686 {
insmod raid
insmod mdraid
insmod ext2
set root=(md3)
search --no-floppy --fs-uuid --set b87bc61c-9b61-4b99-aa49-b12c79836ae7
linux /vmlinuz-2.6.30-1-686 root=/dev/mapper/vgraid-lvroot ro
initrd /initrd.img-2.6.30-1-686
}
menuentry Debian GNU/Linux, with Linux 2.6.30-1-686 (recovery mode) {
insmod raid
insmod mdraid
insmod ext2
set root=(md3)
search --no-floppy --fs-uuid --set b87bc61c-9b61-4b99-aa49-b12c79836ae7
linux /vmlinuz-2.6.30-1-686 root=/dev/mapper/vgraid-lvroot ro single
initrd /initrd.img-2.6.30-1-686
}
menuentry Debian GNU/Linux, with Linux 2.6.26-2-686 {
insmod raid
insmod mdraid
insmod ext2
set root=(md3)
search --no-floppy --fs-uuid --set b87bc61c-9b61-4b99-aa49-b12c79836ae7
linux /vmlinuz-2.6.26-2-686 root=/dev/mapper/vgraid-lvroot ro
initrd /initrd.img-2.6.26-2-686
}
menuentry Debian GNU/Linux, with Linux 2.6.26-2-686 (recovery mode) {
insmod raid
insmod mdraid
insmod ext2
set root=(md3)
search --no-floppy --fs-uuid --set b87bc61c-9b61-4b99-aa49-b12c79836ae7
linux /vmlinuz-2.6.26-2-686 root=/dev/mapper/vgraid-lvroot ro single
initrd /initrd.img-2.6.26-2-686
}
menuentry Debian GNU/Linux, with Linux 2.6.26-1-686 {
insmod raid
insmod mdraid
insmod ext2
set root=(md3)
search --no-floppy --fs-uuid --set b87bc61c-9b61-4b99-aa49-b12c79836ae7
linux /vmlinuz-2.6.26-1-686 root=/dev/mapper/vgraid-lvroot ro
initrd /initrd.img-2.6.26-1-686
}
menuentry Debian GNU/Linux, with Linux 2.6.26-1-686 (recovery mode) {
Bug#551973: Similar issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Not sure if this is the same issue. I just compressed my .VirtualBox directory here (containing VirtualBox's XML config files and all the HDD images/snapshots). Now, when starting Virtualbox, fusecompress bails out. It's final words are: FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::write 0x8fc9860 name: VirtualBox.xml, size: 0xfa8, offset: 0x0 Memory::write(VirtualBox.xml) | m_FileSize: 0x1046, size: 0xfa8, offset: 0x0 FuseCompress::write 0x8fc9860 name: VirtualBox.xml, size: 0x58, offset: 0xfa8 Memory::write(VirtualBox.xml) | m_FileSize: 0x1046, size: 0x58, offset: 0xfa8 FuseCompress::write 0x8fc9860 name: VirtualBox.xml, size: 0x46, offset: 0x1000 Memory::write(VirtualBox.xml) | m_FileSize: 0x1046, size: 0x46, offset: 0x1000 FuseCompress::truncate file VirtualBox.xml, to size: 1046 truncate name: VirtualBox.xml, m_IsCompressed: 1, size: 1046 int Compress::store() void Compress::storeLayerMap(): m_fd: 3 void Compress::storeFileHeader() const: m_fd: 3 getattr name: VirtualBox.xml, m_IsCompressed: 1, m_fh.size: 0x1046 Memory::getattr(0x8fc9860) m_FileSize: 0x1046, m_FileSizeSet: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 getattr name: VirtualBox.xml, m_IsCompressed: 1, m_fh.size: 0x1046 Memory::getattr(0x8fc9860) m_FileSize: 0x1046, m_FileSizeSet: 1 FuseCompress::open 0x8fc9860 name: VirtualBox.xml Compress::open m_refs: 2 FuseCompress::release 0x8fc9860 name: VirtualBox.xml File::release m_refs: 1 Compress::release m_refs: 1, m_IsCompressed: 1 FuseCompress::write 0x8fc9860 name: VirtualBox.xml, size: 0xfa8, offset: 0x0 Memory::write(VirtualBox.xml) | m_FileSize: 0x1046, size: 0xfa8, offset: 0x0 FuseCompress::write 0x8fc9860 name: VirtualBox.xml, size: 0x58, offset: 0xfa8 Memory::write(VirtualBox.xml) | m_FileSize: 0x1046, size: 0x58, offset: 0xfa8 FuseCompress::write 0x8fc9860 name: VirtualBox.xml, size: 0x46, offset: 0x1000 Memory::write(VirtualBox.xml) | m_FileSize: 0x1046, size: 0x46, offset: 0x1000 FuseCompress::truncate file VirtualBox.xml, to size: 1046 truncate name: VirtualBox.xml,
Bug#517969: wordpress: Still failing - missing tinymce/plugins/inlinepopups/skins/clearlooks2/img/drag.gif
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giuseppe Iuculano wrote:
Hi Michel,
Michel Meyers ha scritto:
Hello,
Gears is still failing, it complains about the following file missing:
wp-includes/js/tinymce/plugins/inlinepopups/skins/clearlooks2/img/drag.gif
Might be a bug for tinymce actually as the file doesn't seem to be in there
at all.
I don't know Gears, anyway grepping drag.gif I didn't found anything...
Could
you paste the full error log please?
Hello,
Which log would you want? It states that the file is missing in the
Wordpress admin backend. Gears itself has no log that I can see, and the
apache log just shows a 404 (which is correct as the file is indeed
missing).
On my system, I do find a reference to drag.gif in
/usr/share/wordpress/wp-admin/includes/manifest.php
Line 172:
array('../wp-includes/js/tinymce/plugins/inlinepopups/skins/clearlooks2/img/drag.gif'),
As the file is supposedly a part of tinymce, the bug can be resolved two
ways:
1. remove that reference.
2. have tinymce include the file.
- - Michel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (MingW32)
iEYEARECAAYFAkqOsa4ACgkQ2Vs+MkscAyVftwCglKq5T8XUXm72zPMw+bwC6dbl
hlkAoJgDi4c4kkMU5Md2A9R7x43azdjy
=Ygb1
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517969: wordpress: Still failing - missing tinymce/plugins/inlinepopups/skins/clearlooks2/img/drag.gif
Package: wordpress Version: 2.8.4-1 Severity: normal Hello, Gears is still failing, it complains about the following file missing: wp-includes/js/tinymce/plugins/inlinepopups/skins/clearlooks2/img/drag.gif Might be a bug for tinymce actually as the file doesn't seem to be in there at all. -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-2-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 wordpress depends on: ii apache22.2.12-1 Apache HTTP Server metapackage ii apache2-mpm-prefor 2.2.12-1 Apache HTTP Server - traditional n ii libapache2-mod-php 5.2.6.dfsg.1-1+lenny3 server-side, HTML-embedded scripti ii libjs-cropper 1.2.0-1 JavaScript image cropper UI ii libjs-jquery 1.3.3-1 JavaScript library for dynamic web ii libjs-prototype1.6.0.3-1 JavaScript Framework for dynamic w ii libjs-scriptaculou 1.8.2-1 JavaScript library for dynamic web ii libphp-phpmailer 2.1-1 full featured email transfer class ii libphp-snoopy 1.2.4-1 Snoopy is a PHP class that simulat ii mysql-client 5.0.51a-24+lenny1 MySQL database client (metapackage ii mysql-client-5.0 [ 5.0.51a-24+lenny1 MySQL database client binaries ii php-gettext1.0.7-8 read gettext MO files directly, wi ii php5 5.2.6.dfsg.1-1+lenny3 server-side, HTML-embedded scripti ii php5-gd5.2.6.dfsg.1-1+lenny3 GD module for php5 ii php5-mysql 5.2.6.dfsg.1-1+lenny3 MySQL module for php5 ii tinymce3.2.1.1-0.1 platform independent web based Jav wordpress recommends no packages. Versions of packages wordpress suggests: ii mysql-server 5.0.51a-24+lenny1 MySQL database server (metapackage ii mysql-server-5.0 [mysq 5.0.51a-24+lenny1 MySQL database server binaries -- 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#521445: After the last aptitude update run, dovecot fails to open folders with mailbox doesn't exist
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 * 2009-03-27 16:30, Michel Meyers wrote: Package: dovecot Version: mailbox doesn't exist error on all folders after upgrade Severity: important Hello, I'm not sure if this should be filed against dovecot or dovecot-imapd. After today's package update run, which brought Dovecot to version 1:1.1.12-1, I could not access any of my custom folders in Thunderbird. The Inbox still worked, but any other folders returned mailbox doesn't exist. (This includes folders like Sent and Trash.) Can you please try with the package that I just uploaded to unstable (1.1.13-1)? Thanks. Hello, Just installed 1.1.13-1 and it doesn't have this problem, so I think the bug can be closed. Thanks, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAknQa+EACgkQ2Vs+MkscAyVY+gCeJRSaPVnnUILIrcCzPLz/VNS9 e0YAoJOVvvgKwPFEov3kLmcB1/62fwGb =ZQTT -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#521445: After the last aptitude update run, dovecot fails to open folders with mailbox doesn't exist
Package: dovecot Version: mailbox doesn't exist error on all folders after upgrade Severity: important Hello, I'm not sure if this should be filed against dovecot or dovecot-imapd. After today's package update run, which brought Dovecot to version 1:1.1.12-1, I could not access any of my custom folders in Thunderbird. The Inbox still worked, but any other folders returned mailbox doesn't exist. (This includes folders like Sent and Trash.) I'm using mbox and as a test created a folder called 'tst'. That created both a file called 'tst' and one called '(null)tst' in ~/Mail. Likewise ~/Mail/.imap contains 'INBOX' and '(null)INBOX'. Reverting Dovecot back to 1:1.0.15-2.3 made the problem go away. I'm not sure what those '(null)'-prefixed files are or how to create them (couldn't find anything in the documentation and the changelog, but I might've overlooked something) Here's my dovecot config changes: # 1.0.15: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting: IMAPd ready. mail_privileged_group: mail mail_debug: yes auth default: mechanisms: plain cram-md5 passdb: driver: pam passdb: driver: passwd-file args: /etc/dovecot-passwd userdb: driver: passwd -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#516323: xscreensaver-text --url fails to interpret user/pass from http_proxy var
Package: xscreensaver Version: xscreensaver-text --url does not interpret http_proxy variable correctly Severity: minor Most programs I know accept the following: export http_proxy=http://username:passw...@hostname:port Not so with 'xscreensaver-text --url'. It complains about an 'unrecognized port', probably because it didn't expect a second colon in the line. It would be nice if xscreensaver-text could accept username/password combinations and use them to authenticate against the proxy. -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable'), (500, 'oldstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-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 xscreensaver depends on: ii libc62.7-18 GNU C Library: Shared libraries pn libglib1.2 none (no description available) ii libgtk1.21.2.10-18.1 The GIMP Toolkit set of widgets fo ii libpam0g 1.0.1-5 Pluggable Authentication Modules l ii libxpm4 1:3.5.7-1 X11 pixmap library pn xlib6g none (no description available) Versions of packages xscreensaver recommends: ii libjpeg-progs 6b-14 Programs for manipulating JPEG fil ii netpbm2:10.0-12 Graphics conversion tools ii perl [perl5] 5.10.0-19 Larry Wall's Practical Extraction pn wordlist none (no description available) pn xli | xloadimage | xv none (no description available) Versions of packages xscreensaver suggests: ii elinks [www-browser] 0.12~pre2.dfsg0-1 advanced text-mode WWW browser pn fortunenone(no description available) ii iceweasel [www-browser 3.0.6-1 lightweight web browser based on M ii lynx-cur [www-browser] 2.8.7dev13-1 Text-mode WWW Browser with NLS sup pn qcam | streamernone(no description available) pn xdaliclock none(no description available) pn xscreensaver-glnone(no description available) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#494547: Patch not OK?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is it me or is there a bug in the patch? I applied it and it gives me: server:/usr/share/munin# ./munin-graph syntax error at ./munin-graph line 868, near ); Execution of ./munin-graph aborted due to compilation errors. Original line 868: $_ = encode(utf8, (decode(latin1, $_)); Fixed line: $_ = encode(utf8, (decode(latin1, $_))); (there's an additional parenthesis at the end) Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (MingW32) iEYEARECAAYFAkjKZMQACgkQ2Vs+MkscAyU2nACfZVUkdR91wfSMdUIvDiMhQvaI D1sAoP0t9tGBNXzxAKWpDOvPZadUXd0l =r1hr -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483542: openssl-blacklist: gen_certs.sh does not resume (overwrites already generated certs)
Package: openssl-blacklist
Version: 0.3
Severity: minor
Tags: patch
gen_certs.sh has an if that's probably supposed to make it jump over
existing certs, however the filename it references is missing the .pem
extension. To allow 'resuming' of the certificate generation, please
apply the attached patch to it.
Greetings,
Michel
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-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 openssl-blacklist depends on:
ii openssl 0.9.8g-10+lenny1 Secure Socket Layer (SSL) binary a
ii python 2.5.2-1 An interactive high-level object-o
openssl-blacklist recommends no packages.
-- no debconf information
--- gen_certs.sh2008-05-21 13:12:23.0 +0200
+++ gen_certs.sh2008-05-29 11:46:43.0 +0200
@@ -66,7 +66,7 @@
for i in $(seq 1 32768);
do
-if [ -e certs/cert-$bits-$i-$type ]; then
+if [ -e certs/cert-$bits-$i-$type.pem ]; then
continue
fi
FORCE_PID=$i LD_PRELOAD=$getpid openssl req -newkey rsa:${bits}
-x509 -nodes -keyout certs/key-$bits-$i-$type.pem -subj
'/C=US/ST=Arizona/O=Testlib/OU=Test/CN=CA' -out certs/cert-$bits-$i-$type.pem
Bug#483310: openssl-blacklist: gen_certs.sh generates random certs
Package: openssl-blacklist Version: 0.3 Severity: normal Trying to use gen_certs.sh to build a 4096 key blacklist, I first decided to double check that it would indeed generate vulnerable keys. As far as I can see, the result is a no: sh-3.1# ./gen_certs.sh 1024 sh-3.1# for i in certs//key-* ; do openssl-vulnkey $i ; done | grep -i comprom sh-3.1# (All the keys come back as 'Not blacklisted'.) I've also compared the first 6 keys generated by two separate runs: Not blacklisted: b352e2d6f2fca45c6ee1a9ba8489eea20671c299 certs//key-2048-1-nornd.pem Not blacklisted: 4a3fb7ca9616279c58246898569d70b298985e8c certs//key-2048-2-nornd.pem Not blacklisted: 17e694b5089283b31808e184f6ae86e41fa7cfc5 certs//key-2048-3-nornd.pem Not blacklisted: 07de88f21028b632161582d15d1a46f1629633b5 certs//key-2048-4-nornd.pem Not blacklisted: 6d5bf6b49773be6963c349ac960ffe0e5f212413 certs//key-2048-5-nornd.pem Not blacklisted: 59e4541f5f1ea9cfe8a9d89d11563c22a18053ad certs//key-2048-6-nornd.pem Not blacklisted: d4d13d0a97a864a00a7488166cfff0f7c4643768 certs//key-2048-1-nornd.pem Not blacklisted: ec46e456c29f4922ca8def00182a03f415d50994 certs//key-2048-2-nornd.pem Not blacklisted: 55103f863dcc3a86d5fbc77dfa9011201696087e certs//key-2048-3-nornd.pem Not blacklisted: 7ce62d6e3be99e5ff4a31714288dcaf1158c171e certs//key-2048-4-nornd.pem Not blacklisted: 9faa75991184155fe9b434fbb062a441957434d5 certs//key-2048-5-nornd.pem Not blacklisted: d806c21c2c451fce1bb40e660190c24cbf5a441a certs//key-2048-6-nornd.pem As you can see, the second run generated different keys. Does gen_certs.sh only work when you put a vulnerable version of OpenSSL onto the system? If yes, that should probably be mentioned somewhere as otherwise blacklists generated with it are useless. The code makes it look as if the script removed all randomness by cutting .rnd and using getpid, but as shown above, the resulting keys are still fairly random. (Or did I simply overlook something and am making a huge fool of myself here? That's always a possibility too. ;) ) Greetings, Michel -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-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 openssl-blacklist depends on: ii openssl 0.9.8g-10 Secure Socket Layer (SSL) binary a ii python2.5.2-1An interactive high-level object-o openssl-blacklist recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483310: openssl-blacklist: gen_certs.sh generates random certs
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christoph Martin wrote: | Hi Michel, | | Michel Meyers schrieb: | Package: openssl-blacklist | Version: 0.3 | Severity: normal | | Trying to use gen_certs.sh to build a 4096 key blacklist, I first | decided to double check that it would indeed generate vulnerable keys. | [...] | | As you can see, the second run generated different keys. | | Does gen_certs.sh only work when you put a vulnerable version of OpenSSL | onto the system? | | If I understand the script correctly, this so. It should be called with | a vulnerable version of OpenSSL. OK. In that case this isn't really a bug but me trying to use it wrongly due to that fact not being documented anywhere. A mention in the README.Debian or in the script itself would be nice. | If yes, that should probably be mentioned somewhere as | otherwise blacklists generated with it are useless. The code makes it | look as if the script removed all randomness by cutting .rnd and using | getpid, but as shown above, the resulting keys are still fairly random. | (Or did I simply overlook something and am making a huge fool of myself | here? That's always a possibility too. ;) ) | | We only have blacklists for 1024 and 2048 bit keys at the moment. So | openssl-vulnkey can only detect these compromised keys. I know, which is why I wanted to use gen_certs.sh to generate the vulnerable 4096 bit keys and compare them to the 4096 keys I have. Greetings, ~ Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) iEYEARECAAYFAkg9UQsACgkQ2Vs+MkscAyV+VACaAjquctRhpHJaVsVV/qqiwoON 0KEAnRP7TuN/zwLojxkv7x1X0jjwTPcc =6vno -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479865: spamassassin: Same problem, resolved by clearing directory
Package: spamassassin Version: 3.2.4-1 Followup-For: Bug #479865 I had the same issue on my machine here. sa-update -D stopped with: [16294] dbg: zoom: loading compiled ruleset from /var/lib/spamassassin/compiled/3.002004 /usr/bin/perl: symbol lookup error: /var/lib/spamassassin/compiled/3.002004/auto/Mail/SpamAssassin/CompiledRegexps/body_0/body_0.so: undefined symbol: Perl_Tstack_sp_ptr To clear the error I did: cd /var/lib/spamassassin/compiled/3.002004 rm * -R After that, the problem was gone. Greetings, Michel -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-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 spamassassin depends on: pn libarchive-tar-perl none (no description available) ii libdigest-sha1-perl 2.11-2+b1 NIST SHA-1 message digest algorith ii libhtml-parser-perl 3.56-1+b1 A collection of modules that parse ii libio-zlib-perl 1.09-1 IO:: style interface to gzip/zlib ii libnet-dns-perl 0.63-1+b1 Perform DNS queries from a Perl sc ii libsocket6-perl 0.20-1 Perl extensions for IPv6 ii libsys-hostname-long-perl 1.4-2 Figure out the long (fully-qualifi ii libwww-perl 5.812-1WWW client/server library for Perl ii perl 5.10.0-10 Larry Wall's Practical Extraction ii perl-modules [libio-zlib-perl 5.10.0-10 Core Perl modules Versions of packages spamassassin recommends: ii gcc 4:4.2.2-2 The GNU C compiler ii gnupg 1.4.6-2.2 GNU privacy guard - a free PGP rep ii libc6-dev 2.7-10 GNU C Library: Development Librari ii libmail-spf-perl 2.005-1Perl implementation of Sender Poli ii libsys-syslog-perl0.24-1+b1 Perl interface to the UNIX syslog( ii make 3.81-4 The GNU version of the make util ii re2c 0.13.3-1 tool for generating fast C-based r ii spamc 3.2.4-1Client for SpamAssassin spam filte -- debconf information: spamassassin/upgrade/2.40w: spamassassin/upgrade/2.42m: No spamassassin/upgrade/2.40: spamassassin/upgrade/cancel: Continue spamassassin/upgrade/2.42: No spamassassin/upgrade/2.42u: No -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469136: pymsnt: Changing the config made it work
Package: pymsnt Followup-For: Bug #469136 Hello, I just fiddled around with my configuration file for pymsnt (/etc/pymsnt.conf.xml), changing the 'host' setting (public IP or DNS name) and now, after a restart of the service, it works fine. I might have changed some other value too, not sure, but it ever since, I've been able to connect to MSN without a problem. Greetings, Michel -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-k7 (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 pymsnt depends on: ii adduser 3.106 add and remove users and groups ii python 2.4.4-6 An interactive high-level object-o ii python-central 0.5.15-0.1 register and build utility for Pyt ii python-crypto2.0.1+dfsg1-2.1 cryptographic algorithms and proto ii python-pyopenssl 0.6-2.3 Python wrapper around the OpenSSL ii python-twisted 2.5.0-2 Event-based framework for internet Versions of packages pymsnt recommends: ii python-imaging1.1.6-1Python Imaging Library -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469951: molly-guard: Doesn't work in 'screen'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 martin f krafft wrote: | tag 469951 patch confirmed | thanks | | also sprach Michel Meyers [EMAIL PROTECTED] [2008.03.08.0943 +0100]: | When logged in remotely to a machine and opening up a screen (ie the | utility screen), molly guard doesn't intercept the reboot command | (probably others too). Maybe there's a way to have it detect 'screen' | (optionally?). | | The reason is simply that screen creates a new PTY, and we cannot | really figure out that it's a child of sshd. But there is the | environment, and we can just try both. Sorry for not getting back earlier. I've tried the patch on two systems now and it's working fine there. (even when in screen, molly guard intercepts my commands) Greetings, ~Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (MingW32) iEYEARECAAYFAkfX9+IACgkQ2Vs+MkscAyWqVgCeLjz78jgRP5aGG1spJuxX/RcM JwwAoJM7TFd5LTTKo/ylxhbMB8iKG3AP =D3Pm -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469951: molly-guard: Doesn't work in 'screen'
Package: molly-guard Version: 0.3-2 Severity: minor When logged in remotely to a machine and opening up a screen (ie the utility screen), molly guard doesn't intercept the reboot command (probably others too). Maybe there's a way to have it detect 'screen' (optionally?). -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-k7 (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 molly-guard depends on: ii sysvinit 2.86.ds1-53 System-V-like init utilities molly-guard recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#469136: pymsnt: Same problem on my machine
Package: pymsnt Version: 0.11.3-1 Followup-For: Bug #469136 I have the same problem on my machine. Couldn't find a resolution for it yet (the old version doesn't run here any more) -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-k7 (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 pymsnt depends on: ii adduser 3.105 add and remove users and groups ii python 2.4.4-6 An interactive high-level object-o ii python-central 0.5.15-0.1 register and build utility for Pyt ii python-crypto2.0.1+dfsg1-2.1 cryptographic algorithms and proto ii python-pyopenssl 0.6-2.3 Python wrapper around the OpenSSL ii python-twisted 2.5.0-2 Event-based framework for internet Versions of packages pymsnt recommends: ii python-imaging1.1.6-1Python Imaging Library -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466415: zabbix-frontend-php: syntax error in copt.lib.php on line 112
Package: zabbix-frontend-php Version: 1.4.4-3 Severity: important On systems running php4, this problem occurs: http://www.zabbix.com/forum/archive/index.php/t-8582.html My example system: Apache 1.3.34-4.1 libapache-mod-php4 6:4.4.6-2+b1 The above URL also mentions a fix, changing all the: /* protected */ static to /* protected static */ in copt.lib.php. Alternatively, make the package depend on PHP5 to work around this issue. -- System Information: Debian Release: unstable/sid Architecture: i386 (i686) Kernel: Linux 2.6.22-3-k7 (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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427173: libgphoto2-2: Add support for Nikon Coolpix P5000 to udev rules
Package: libgphoto2-2
Version: 2.3.1-3
Severity: wishlist
Tags: patch
Please add support for Nikon Coolpix P5000 (04b0:015b) to the udev rules.
-- System Information:
Debian Release: lenny/sid
APT prefers stable
APT policy: (700, 'stable'), (650, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-4-k7 (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 libgphoto2-2 depends on:
ii adduser 3.102 Add and remove users and groups
ii libc6 2.5-9+b1 GNU C Library: Shared libraries
ii libexif12 0.6.13-5 library to parse EXIF files
ii libgphoto2-port0 2.3.1-3gphoto2 digital camera port librar
ii libjpeg62 6b-13 The Independent JPEG Group's JPEG
ii libltdl3 1.5.22-4 A system independent dlopen wrappe
Versions of packages libgphoto2-2 recommends:
ii udev 0.105-4/dev/ and hotplug management daemo
-- no debconf information
--- libgphoto2.rules2007-06-02 12:37:25.0 +0200
+++ libgphoto2.rules2007-06-02 12:37:25.0 +0200
@@ -474,6 +474,7 @@
ATTRS{idVendor}==04b0, ATTRS{idProduct}==0406, MODE=0660, GROUP=plugdev
ATTRS{idVendor}==04b0, ATTRS{idProduct}==040e, MODE=0660, GROUP=plugdev
ATTRS{idVendor}==04b0, ATTRS{idProduct}==0412, MODE=0660, GROUP=plugdev
+ATTRS{idVendor}==04b0, ATTRS{idProduct}==015b, MODE=0660, GROUP=plugdev
ATTRS{idVendor}==04fc, ATTRS{idProduct}==504a, MODE=0660, GROUP=plugdev
ATTRS{idVendor}==07b4, ATTRS{idProduct}==0105, MODE=0660, GROUP=plugdev
ATTRS{idVendor}==07b4, ATTRS{idProduct}==0100, MODE=0660, GROUP=plugdev
Bug#426157: nvidia-graphics-legacy-modules-i386: New release available: 1.0-7185
Package: nvidia-graphics-legacy-modules-i386 Severity: wishlist There's a new release available at http://www.nvidia.com/object/linux_display_ia32_1.0-7185.html This supposedly fixes issues with newer kernels and X.Org -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419888: Maybe working with newer version of spandsp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've managed to recompile asterisk with a snapshot release of spandsp (probably what is to be 0.0.4 once it is released) http://www.soft-switch.org/downloads/spandsp/spandsp-0.0.4pre1.tgz I used: http://www.soft-switch.org/downloads/snapshots/spandsp/spandsp-20070427.tar.gz In addition to that, you need new apps from: http://www.soft-switch.org/downloads/snapshots/spandsp/test-apps-asterisk-1.4/ The patch (use with -p0 in asterisk's root source dir) doesn't apply cleanly (but the failed hunks can be added with some manual work). Apart from that plc.h needs to be copied from that spandsp archive to include/asterisk/plc.h. Note though that I haven't performed anything but basic tests on the app (it doesn't crash on me any more and seems to try to accept a fax). Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGRIIH2Vs+MkscAyURAsFJAJ9PCn+t+zPmAsc704EJFrRRWzFU7ACg1VSk zPxSvNBT0eIX03K7hqYCiAM= =AEGW -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419980: zabbix-server-mysql: Shuts down during MySQL upgrades
Package: zabbix-server-mysql Severity: normal /tmp/reportbug-zabbix-server-20070419-6886-TnBhAW -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419888: asterisk-app-fax: Doesn't work with Asterisk 1.4.x
Package: asterisk-app-fax Version: 0.0.20060218-4 Severity: grave Justification: renders package unusable After installing asterisk 1.4.2~dfsg-4, app-rxfax and app-txfax fail to load with: [Apr 18 15:24:44] WARNING[29481] loader.c: Module 'app_rxfax.so' did not register itself during load [Apr 18 15:24:44] WARNING[29481] loader.c: Module 'app_rxfax.so' could not be loaded. [Apr 18 15:24:44] WARNING[29481] loader.c: Module 'app_txfax.so' did not register itself during load [Apr 18 15:24:44] WARNING[29481] loader.c: Module 'app_txfax.so' could not be loaded. Not sure which package should handle this but I guess some dependency directives are needed to make sure these packets stay in sync. (I'm currently trying to manually compile a newer version of the spandsp apps but without success so far) Greetings, Michel -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-k7 (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 asterisk-app-fax depends on: ii libc6 2.5-1GNU C Library: Shared libraries ii libspandsp1 0.0.2pre26-1 Telephony signal processing librar Versions of packages asterisk-app-fax recommends: ii gs-common 0.3.11 Common files for different Ghostsc ii libconfig-tiny-perl 2.08-1 Read/Write .ini style files with a ii libfile-sync-perl 0.09-4 Perl interface to sync() and fsync ii liblocale-gettext-perl1.05-1 Using libc functions for internati ii libmime-lite-perl 3.01-8 Perl5 module for convenient genera ii libpaper-utils1.1.21 Library for handling paper charact ii libtiff-tools 3.8.2-7TIFF manipulation and conversion t ii psutils 1.17-24A collection of PostScript documen -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405030: Comment is now wrong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Very very very minor detail here, the new comment in /etc/greylistd/config is wrong. I quote: # Default is 1 hour = 600 seconds Should probably be: # Default is 10 minutes = 600 seconds Sorry for the nitpicking. - - Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (MingW32) - GPGrelay v0.959 iD8DBQFF1BGO2Vs+MkscAyURAoTqAKCPxFr1BiPOJMY0eESB6dZNbQMOtACcD4x+ OjYcxRmTMurmpssSvmeZ19A= =yO2i -END PGP SIGNATURE- --- config 2007-02-15 08:48:47.0 +0100 +++ config 2007-02-15 08:49:01.0 +0100 @@ -5,7 +5,7 @@ [timeouts] # Initial delay before previously unknown triplets are allowed to pass -# Default is 1 hour = 600 seconds +# Default is 10 minutes = 600 seconds retryMin = 600 # Lifetime of triplets that have not been retried after initial delay config.patch.asc Description: Binary data
Bug#401393: Please test the attached patch for against lilo 22.7.3-1.3
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Loïc Minier wrote: Could people experiencing this bug please test the attached lilo_22.7.3-1.4.diff against lilo 22.7.3-1.3? Seems to be working on my box. At least I didn't get any error messages when running lilo, and it rebooted properly. (That said, there was no change to the kernel since the last time lilo worked, so the latter might just be coincidence.) Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (MingW32) - GPGrelay v0.959 iD8DBQFFwL+o2Vs+MkscAyURAuStAJ9fgALLaalTm7JCiXnExiWWBOhvgwCfZ/e4 EgZI52hz/x64P+4XTBmEml4= =54Hf -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401393: Got the same issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just adding myself here to receive bug notifications (hope that actually works by adding a notice), I have the same issue than the first submitter, LVM on RAID1 and lilo fails with: device-mapper: table ioctl failed: No such device or address Fatal: device-mapper: dm_task_run(DM_DEVICE_TABLE) failed Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (MingW32) - GPGrelay v0.959 iD8DBQFFgnrH2Vs+MkscAyURAg9EAJoDI7mqYUWn1ACPpirRq+44N8GnGgCg9EYT gceGtFd5XASNyJ85qNYT7UY= =d29R -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402731: xmltv: 0.5.45 is available upstream
Package: xmltv Version: 0.5.45 is available upstream Severity: wishlist Just in case this went unnoticed, upstream seems to have released version 0.5.45: http://sourceforge.net/project/showfiles.php?group_id=39046 http://sourceforge.net/project/shownotes.php?group_id=39046release_id=468231 Thanks for your work on maintaining this package. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-k7 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#401042: molly-guard: Shield poweroff command as well
Package: molly-guard Version: 0.2.1-1 Severity: wishlist It would be great if molly-guard could also shield the poweroff command from being inadvertedly launched remotely. I might be wrong but I think this should be easy to implement by modifying /usr/share/molly-guard/shutdown like this: -- --- shutdown2006-11-30 14:56:30.0 +0100 +++ shutdown2006-11-30 14:56:44.0 +0100 @@ -15,7 +15,7 @@ EXEC=/sbin/$CMD case $CMD in - halt|reboot|shutdown) + halt|poweroff|reboot|shutdown) if [ ! -f $EXEC ]; then echo E: $ME: not a regular file: $EXEC 2 exit 4 -- and then adding a symlink in /usr/sbin like this: cd /usr/sbin ln -s ../share/molly-guard/shutdown poweroff Greetings, Michel -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages molly-guard depends on: ii sysvinit 2.86.ds1-35 System-V-like init utilities molly-guard recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374506: /usr/bin/tv_grab_de_tvtoday: tv_grab_de_tvtoday replaces some titles with 'REF'
Package: xmltv-util Version: 0.5.43-1 Severity: normal File: /usr/bin/tv_grab_de_tvtoday Using the latest tv_grab_de_tvtoday, some titles get grabbed incorrectly (output is titleREF/title instead of containing the actual title). The command is invoked with: tv_grab_de_tvtoday --output all.xml --days 7 --slow --share /usr/share/xmltv/ Replacing tv_grab_de_tvtoday with the latest version in CVS (rev 1.45 from http://xmltv.cvs.sourceforge.net/xmltv/xmltv/grab/de_tvtoday/tv_grab_de_tvtoday.in ) seems to fix the issue. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xmltv-util depends on: ii libarchive-zip-perl 1.16-1 Module for manipulation of ZIP arc ii libcompress-zlib-perl 1.41-1 Perl module for creation and manip ii libdate-manip-perl5.44-2 a perl library for manipulating da ii libhtml-parser-perl 3.54-1 A collection of modules that parse ii libhtml-tableextract-perl 2.07-0.1 Perl module that simplifies extrac ii libhtml-tree-perl 3.19.01-2 represent and create HTML syntax t ii libhttp-cache-transparent-per 0.7-1 Perl module used to transparently ii libio-stringy-perl2.110-1Perl5 modules for IO from scalars ii libsoap-lite-perl 0.67-1 Client and server side SOAP implem ii libterm-readkey-perl 2.30-3 A perl module for simple terminal ii libwww-mechanize-perl 1.18-1 Automate interaction with websites ii libwww-perl 5.805-1WWW client/server library for Perl ii libxml-libxml-perl1.58-3 Perl module for using the GNOME li ii libxml-parser-perl2.34-4 Perl module for parsing XML files ii libxml-twig-perl 1:3.25-1 Perl module for processing huge XM ii libxml-writer-perl0.600-3Perl module for writing XML docume ii libxmltv-perl 0.5.43-1 Perl libraries related to the XMLT ii perl 5.8.8-4Larry Wall's Practical Extraction ii perl-modules 5.8.8-4Core Perl modules Versions of packages xmltv-util recommends: ii liblingua-preferred-perl 0.2.4-2Perl module which allows language ii libterm-progressbar-perl 2.09-4 Perl module to print a progress ba ii libtext-kakasi-perl 1.05-4 KAKASI interface for scripting lan ii libunicode-string-perl2.09-1 Perl modules for Unicode strings -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#373566: zabbix-frontend-php expects the randomly generated db password before it's generated
Package: zabbix-frontend-php Version: 1:1.1-4 Severity: important Hello, Installing zabbix-server-mysql, which pulled in the frontend automatically, the frontend package got unpacked and set up before the actual server and started prompting me for MySQL database access configuration (which hadn't been defined yet). In addition to that, I fail to see how the user can know the MySQL password if he/she tells the server package to generate it randomly. (Apart from manually looking it up in /etc/zabbix/zabbix_server.conf after the installation of course.) dpkg-reconfigure zabbix-frontend-php doesn't seem to do anything either, I have to purge the package and reinstall it to be able to reenter the database information. Greetings, Michel -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages zabbix-frontend-php depends on: ii apache [httpd] 1.3.34-2 versatile, high-performance HTTP s ii debconf [debconf-2.0] 1.5.2Debian configuration management sy ii php44:4.4.2-1server-side, HTML-embedded scripti ii php4-cgi4:4.4.2-1+b1 server-side, HTML-embedded scripti ii php4-gd 4:4.4.2-1+b1 GD module for php4 ii php4-mysql 4:4.4.2-1+b1 MySQL module for php4 Versions of packages zabbix-frontend-php recommends: ii mysql-server 5.0.22-2 mysql database server (current ver ii mysql-server-5.0 [mysql-serve 5.0.22-2 mysql database server binaries ii zabbix-server-mysql 1:1.1-4software for monitoring of your ne -- debconf information: * zabbix-frontend-php/database-password: (password omitted) * zabbix-frontend-php/database-user: zabbix * zabbix-frontend-php/database-type: MYSQL * zabbix-frontend-php/database-server: localhost * zabbix-frontend-php/restart-webserver: true * zabbix-frontend-php/database-name: zabbix * zabbix-frontend-php/reconfigure-webserver: apache, apache-ssl, * apache-perl, apache2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#362203: flashplugin-nonfree: Same problem here, download server is NXDOMAIN
Package: flashplugin-nonfree Followup-For: Bug #362203 Hello, I have the same problem here and for me fpdownload.macromedia.com doesn't resolve (macromedia.com does). -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360696: exim4-daemon-heavy: Failed to get write lock forretry.lockfile / exim process hangs with 100% CPU
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Metzler wrote: On 2006-04-04 Michel Meyers [EMAIL PROTECTED] wrote: Package: exim4-daemon-heavy Version: 4.60-4 Severity: normal Hello, I'm having a similar problem as the one mentioned in Bug 314356 : I communicate a lot with people defined on an SMTP server that uses greylisting and whenever that server rejects one of my outgoing e-mails (meaning that exim has to retry on my side), the respective exim process gets stuck with 100% CPU usage and the only way to get rid of it is to kill it with signal 9. While the stuck process is there, the mainlog keeps mentioning messages like these: [...] What does exiwhat say about the stuck process? cu andreas Sorry for the late reply, was out of town for a few days. It states: 31441 tidying up after delivering 1FT0NS-0008AT-0D Greetings, Michel P.S. Resending, I think I inadvertedly encrypted the mail. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) - GPGrelay v0.959 iD8DBQFEOqTh2Vs+MkscAyURAk+uAJ4r1WznxlSikk7nTtqbje5ZjaXokACghPyO SH7YvqyfQtuY3jBQDsgjhZM= =I+f2 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360696: exim4-daemon-heavy: Failed to get write lock forretry.lockfile / exim process hangs with 100% CPU
-BEGIN PGP MESSAGE- Version: GnuPG v1.4.2 (MingW32) - GPGrelay v0.959 hQQOA+qVrMD51YUvEBAAw4MZr5CH6rmyEy03HcPZZXJ4JzBBuHEMfTWmlXbKsJ/w aob/Av8z3iUF12RMZQf4BsmSfYTSsIl7/eYn4Wha6nM3DGP8I/lqtyq+2pD/Rs9c kz7fvKKrGeKrHeN9Hu+kv78lQQRykJsTNIS6Ws5NtVDMuxHsG4T+irrCd3StH8Dw 9szf1nCuoabbE092FUebAVn1To7EcEsk+oevReknkn03QaAjCv2tNBR5FokWCxAP 6dEqz2bQIEJahrXPEiUNRqGxoPOdpfgtyeC9NTpQkq0I+klvsvyNtZzhOqFEzYSC GESn9wSvn3tEEryVUwOjyocY+42HQYr/YIIvnbIrcaVN7ZJSiIPz4UgFZ0iTqAdH Ri4TzqgKPA59KitdPOi7A5ylJjDmOxXgm1rHMVHE3MluxAvfQck1shT+idAxiBMF EeVtEot/4RB0E1d0HS+LvGapVf2uxmAkwzMRFE6p4hANxToZvorE2b5PxqkXC9aX qNtV/deu6zz+/wD/styqiLm+Qk87URwoN2JoYIMOVliZ6RreCq0tKCcdaOOw5ZR6 MLbPfFZLZrbW2TrQ1L01HQx7x0fgKqbXDHTazUPRh21waLI+M42bastmNV0nGlOH B6RYHEMEGzbouTXsW/xFiRi0/2vnKrHGhKxCTuqQAftvWr6UREDeIGYHaBcY1dMQ AJm50At04htoB/NTUaQnnCgw31Ul6iVdzn/B3h8L48YN8DYaU/H3n7TWpfAdOAIA LB5BkR8QRJgbR3iHv45ae/F/TK1zTTEtUY8zH1oxjVSeV5nUPhhMirvaQL3TcdvU e8BSWa2orERV6n6GysJyIqXmxxmHQHnWycfNvD5UK0wHJfpfE4R1Wuo2yK+lZDL4 x7jpGqEZp8R2wVeaFmEgtgXOVDQe8/A/TxaTi7D9qnloAllDqwZJCCYZtXebFR6r P48rKk74Aui6H1AiP4lnoJuoJHF/tLV7Irpf04wLES+yn2NhgL5MBc4R9QGr4rCl uYKFrsvnKPxCX1HrFbzX9iIpxPKpJrvwgjALKNwcZdd5ql3l0mbZxKvFPGUY1pfe cKAzb3mzKI3GUD3/4Dr0Xkn2kXsfhJlibbCbvRQ0emK0VHPdnWtBl0tarjKRnzBY ZNi9A3uPg7tTgUbenedCpowDGPs0bMNTZ+TyZE3XbD1sf8DkN7GNE1RW1ESQTlWH O3sUniIP1NcstCxY4umMnQJOqqf6jcKM60nPHH9Oy8EnpjqrNeumbrj/q3JIrH3y 56ZtqFpMdHKJlt3EUnidj/l+WvD5cFxeEiK0UB9pLGCqJ7pn5Ae9cDgShwTi4YJZ h6g6QvJGR6w1MuJ7xh+j3PhP/o31SPXwVQIrgIovSewI0ukB2CHneo7WRJN+GyB4 f3IvnTcDQ1a1BPx8JlvVS0p5ALa4L/lTXFxcEA8IWBDbjVdTGtkEIMainkgk65qc imVRlSw7kRguUTVW88jAm6829P96gROAJux2hwDd5UYOQJbk/NDkffdVNE1zn9Iw vzOh+kknENzaZToPY1pHGXcT28edKlrX/l4bpKK0mQAI3mUzl6IzQe27efv8tMda PmAKxZaPzvBuM84XfCrV6mHoe57oYVj0swY669UzKErYkA+vr8s3wiCD2RQXMk0f Xjv1DjrH/sDvs9rvTifTtrriGXm+Wd61AxOmCiU0pfaolq72tcs6YY7EvvB1lvIy bOsGoSzoXGHaTa90YaOLmpyg/zA4jszbNNa4hPzL54X6xwXQhStKXKUWgfmI/NIn fQQC9Vg5TRNZ918wAPXQNmaqCo5kw8t8ZipeJzIZkU9+x0RS9YkAGfuScZ3Argw4 C7G8zLKsjWv8QZivaqAGNZXDwD614px8W63h3WewqTfAH6tlWCfJsdLmM6Of9M7i Ad2RyQZwyQNhW27DDZqFbQZIZyKTAp2Ti4EgvAYZMOrNXG3J0Vyiw/RImGo7CWOE XUwD0lkdk835Fa8fKwBVK9snkfLfLlbf2sHYoMliOOGo58zrLmn4kSazdPhojEm2 JROdhgfNokEh9hUfwDoROOcMQcALrZy676SICk8E+z2pHlTYBbfehyBODNLZECka 62J6ZLuue6o7UxseC2LW66vjuFfS4cEi5fckHftuwUwSezmL3Zgz2fOvU/T4oh3z mL/HDEAXUWam3ae6sWTSpcACZLyo6RvU5D1MZD5kdFMgwPh4akizqbVYYChuKQkk o3naCRTLYLLWlVCk33UuJvEb7V4JQZ+tflsA3WE5/2VCCHO9s+IrScbxNuAmENDg Kn2Yt9P9bjOUZxkGbZBe4Tr48Fjbe/0BJDUXMYQzCEA= =PHU+ -END PGP MESSAGE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360696: exim4-daemon-heavy: Failed to get write lock for retry.lockfile / exim process hangs with 100% CPU
Package: exim4-daemon-heavy Version: 4.60-4 Severity: normal Hello, I'm having a similar problem as the one mentioned in Bug 314356 : I communicate a lot with people defined on an SMTP server that uses greylisting and whenever that server rejects one of my outgoing e-mails (meaning that exim has to retry on my side), the respective exim process gets stuck with 100% CPU usage and the only way to get rid of it is to kill it with signal 9. While the stuck process is there, the mainlog keeps mentioning messages like these: 2006-04-04 09:13:33 1FQfgD-0002kv-EZ Failed to get write lock for /var/spool/exim4/db/retry.lockfile: timed out 2006-04-04 09:13:48 1FQfhL-00035E-Ay Failed to get write lock for /var/spool/exim4/db/retry.lockfile: timed out 2006-04-04 09:14:48 1FQfhL-00035E-Ay Failed to get write lock for /var/spool/exim4/db/retry.lockfile: timed out Other messages are being delivered though but the message that got rejected by the greylisting server remains stuck until I kill said process to have it delivered again (at which time the greylisting server usually lets it through). Here's an example log entry of a message getting rejected (causing the process to go to 100% CPU): 2006-04-04 09:31:40 1FQ2wq-0005Kt-8R == [EMAIL PROTECTED] R=dnslookup T=remote_smtp defer (-44): SMTP error from remote mail server after RCPT TO:[EMAIL PROTECTED]: host mail.removed.de [xx.xxx.xxx.xx]: 451 GL - temporary problem. Please try again later. Could this be a configuration issue on my side or is it a problem with the code? I use greylistd, amavis-new and spamassassin on my end and the server hosts multiple domains (lookups done through static alias files for those). Greetings, Michel -- Package-specific info: Exim version 4.60 #1 built 22-Feb-2006 10:49:24 Copyright (c) University of Cambridge 2005 Berkeley DB: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003) Support for: crypteq iconv() IPv6 PAM Perl GnuTLS move_frozen_messages Content_Scanning Old_Demime Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql Authenticators: cram_md5 cyrus_sasl plaintext spa Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' dc_eximconfig_configtype='internet' dc_other_hostnames='tcnnet.com:tcnnet.dyndns.org' dc_local_interfaces='0.0.0.0.25 : 127.0.0.1.10025' dc_readhost='' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='' dc_smarthost='' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='' dc_mailname_in_oh='true' mailname:tcnnet.dyndns.org -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages exim4-daemon-heavy depends on: ii exim4-base 4.60-4 support files for all exim MTA (v4 ii libc62.3.6-3 GNU C Library: Shared libraries an ii libdb4.2 4.2.52-23.1 Berkeley v4.2 Database Libraries [ ii libgnutls12 1.2.9-2 the GNU TLS library - runtime libr ii libldap2 2.1.30-13 OpenLDAP libraries ii libmysqlclient15 5.0.18-9mysql database client library ii libpam0g 0.79-3.1Pluggable Authentication Modules l ii libpcre3 6.4-1.1 Perl 5 Compatible Regular Expressi ii libperl5.8 5.8.8-3 Shared Perl library ii libpq4 8.1.0-3 PostgreSQL C client library ii libsasl2 2.1.19-1.9 Authentication abstraction library exim4-daemon-heavy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#360696: exim4-daemon-heavy: Failed to get write lock forretry.lockfile / exim process hangs with 100% CPU
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marc Haber wrote: On Tue, Apr 04, 2006 at 09:36:52AM +0200, Michel Meyers wrote: Could this be a configuration issue on my side or is it a problem with the code? I use greylistd, amavis-new and spamassassin on my end and the server hosts multiple domains (lookups done through static alias files for those). Is TLS in use? Does your system have enough entropy? Hello, Yes, TLS is enabled. How much entropy is 'enough'? # cat /proc/sys/kernel/random/entropy_avail 1885 According to munin the avg entropy available is 213 and the minimum in the last 24 hours was 47. Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) - GPGrelay v0.959 iD8DBQFEMnlG2Vs+MkscAyURAqtHAKCEfKPM0ONIjCmJJJlCOIPSeuW3kQCgr0xa 6IdhXRj4sU5j+851f3xwpog= =/nBu -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#242907: bittorrent: Can probably be closed
Package: bittorrent Version: 3.4.2-6 Followup-For: Bug #242907 Given the fact that nobody else was able to reproduce this and that I'm not using bittorrent any more, I guess this can be closed. (I'm suspecting it to have been an issue with the trackers at the time) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages bittorrent depends on: ii python2.3.5-3An interactive high-level object-o Versions of packages bittorrent recommends: ii mime-support 3.35-1 MIME files 'mime.types' 'mailcap -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319995: clusterssh: Fixed
Package: clusterssh Version: 3.18.1-1 Followup-For: Bug #319995 Don't ask me how but the problem can't be reproduced on my system any more. I guess it got fixed with a later release of clusterssh or one of its dependencies but anyway, the bug can probably be closed. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages clusterssh depends on: ii libx11-protocol-perl 0.54-2 Perl module for the X Window Syste ii openssh-client 1:4.2p1-5 Secure shell client, an rlogin/rsh ii perl-tk 1:800.025-2 Perl module providing the Tk graph ii xterm6.8.2.dfsg.1-11 X terminal emulator clusterssh recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#329907: kernel-patch-2.6-reiser4: 2.6.14 has entered testing
Package: kernel-patch-2.6-reiser4 Version: 20050715-1 Followup-For: Bug #329907 2.6.14 has entered testing so I guess we'll need support for that one too (the patch won't apply to it right now). -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-patch-2.6-reiser4 depends on: ii bash 3.1-1 The GNU Bourne Again SHell ii grep-dctrl2.6.7 Grep Debian package information ii patch 2.5.9-2Apply a diff file to an original kernel-patch-2.6-reiser4 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#342797: gdhcpd: Doesn't find dhcpd even though it's installed
Package: gdhcpd Version: 0.2.8-1 Severity: normal Right after starting, the GUI displays the following error message: ISC DHCPD is not installed or not in your path The problem seems to be that it is looking for the dhcpd binary, but that one's called dhcpd3 (/usr/sbin/dhcpd3 to be exact) in Debian etch. A simple symlink in /usr/sbin is enough to make the message go, alternatively you could add code to check for both dhcpd and dhcpd3 (maybe upstream?). Greetings, Michel -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages gdhcpd depends on: ii dhcp3-server 3.0.3-5DHCP server for automatic IP addre ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libc6 2.3.5-8GNU C Library: Shared libraries an ii libglib2.0-0 2.8.3-1The GLib library of C routines ii libgtk2.0-0 2.6.10-1 The GTK+ graphical user interface ii libpango1.0-0 1.8.2-3Layout and rendering of internatio gdhcpd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#314356: Same problem here
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I also see this happening here from time to time (same error messages about the lock, exim process eating 99% CPU and requiring a kill -9). If I am not mistaken it occurs when Exim cannot deliver a message immediately (for example if I send something to a server using greylisting). Usually just killing the offending process with -9 is enough to get everything going again. Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (MingW32) - GPGrelay v0.959 iD8DBQFDWpyF2Vs+MkscAyURAvxAAKCEhcdjWZ4CJDmBqyhBjBSkvVieRwCeJzq9 2ktvvMEkCyL4q/bddUqNRz8= =tZb6 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#331225: kernel-patch-2.6-reiser4: Kernel 2.6.12 compilation fails with reiser4 patch applied
Package: kernel-patch-2.6-reiser4 Version: 20050715-1 Severity: important Justification: fails to build from source When applying the reiser4 patch from this package to the linux-sources-2.6.12, compilation fails with the following messages: - LD .tmp_vmlinux1 fs/built-in.o: In function `gzip1_alloc': compress.c:(.text+0x76268): undefined reference to `zlib_deflate_workspacesize' compress.c:(.text+0x7627b): undefined reference to `zlib_deflate_workspacesize' fs/built-in.o: In function `gzip1_compress': compress.c:(.text+0x7641e): undefined reference to `zlib_deflateInit2_' compress.c:(.text+0x76486): undefined reference to `zlib_deflateReset' compress.c:(.text+0x764ba): undefined reference to `zlib_deflate' make[1]: *** [.tmp_vmlinux1] Error 1 make[1]: Leaving directory `/usr/src/linux-source-2.6.12' make: *** [stamp-build] Error 2 - Here's what leads to the above: cd /usr/src tar xjvf linux-source-2.6.12.tar.bz2 ln -s /usr/src/linux-source-2.6.12 linux cd linux cp /boot/config-2.6.12-1-k7 .config ../kernel-patches/all/apply/reiser4 make oldconfig (reply 'Yes' when prompted for Reiser4 and no to Reiser4 debugging) make-kpkg kernel-image I also checked .config and found these lines: CONFIG_ZLIB_INFLATE=y CONFIG_ZLIB_DEFLATE=m Switching the latter to 'y' unfortunately didn't help either. (I hope I'm not doing something wrong here) -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-patch-2.6-reiser4 depends on: ii bash 3.0-16 The GNU Bourne Again SHell ii grep-dctrl2.6.7 Grep Debian package information ii patch 2.5.9-2Apply a diff file to an original kernel-patch-2.6-reiser4 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#331225: Update: compiling as module works
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just tried compiling reiser4 as module, that worked, so this bug only applies when trying to compile reiser4 into the kernel. Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) - GPGrelay v0.959 iD8DBQFDP/bT2Vs+MkscAyURAqWPAKDPY8kIR4NHh69uIN655mdV27m0PACgxSEN ybLqIvJVBcuAjbEG7YzRepU= =Wy47 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324572: apt-cacher: Seeing the same problem here
Package: apt-cacher Version: 1.0.11 Followup-For: Bug #324572 I'm also seeing this on my box. My apache error.log contains these lines: Unable to bind socket (port 3142), /usr/share/apt-cacher/apt-cacher.pl not started. Compilation failed in require at /usr/share/apt-cacher/apt-cacher.pl line 5. It makes no difference whether I run apt-cacher in daemon mode or not. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages apt-cacher depends on: ii bzip2 1.0.2-8high-quality block-sorting file co ii libwww-perl 5.803-4WWW client/server library for Perl ii perl 5.8.7-3Larry Wall's Practical Extraction apt-cacher recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312973: kernel-image-2.6.11-1-k7: Same problem here.
Followup-For: Bug #312973 Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-7 Hello, I can't vouch for the sound playback problems but I'm seeing the clock drift problem on my system as well: processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 2600+ stepping: 0 cpu MHz : 1913.322 cache size : 512 KB nForce2 Chipset. It used to work fine in 2.6.8 and lower, the problem appeared after going to 2.6.11. Though I fear this is upstream, please let me know if I can provide any system information useful in debugging this. Greetings, Michel -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kernel-image-2.6.11-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.81.1 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo kernel-image-2.6.11-1-k7 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#321232: qemu: New upstream version 0.7.1 available
Package: qemu Severity: wishlist Just FYI, a new upstream version (0.7.1) has been released: http://fabrice.bellard.free.fr/qemu/download.html From the Changelog: - read-only Virtual FAT support (Johannes Schindelin) - Windows 2000 install disk full hack (original idea from Vladimir N. Oleynik) - VMDK disk image creation (Filip Navara) - SPARC64 progress (Blue Swirl) - initial MIPS support (Jocelyn mayer) - MIPS improvements (Ralf Baechle) - 64 bit fixes in user networking (initial patch by Gwenole Beauchesne) - IOAPIC support (Filip Navara) Greetings, Michel P.S. and while I'm at it: Thanks for the great packaging work. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#319995: clusterssh: Input into textbox is ignored
Package: clusterssh Version: 3.17.1-1 Severity: important Connecting to servers works fine (terminal windows pop up and ask for password) but trying to type something into the textbox that's supposed to send input to all of them yields no result (one can type manually into the separate terminal windows though). This problem appeared with the latest versions of cssh, the previous ones (2.something?) worked fine. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages clusterssh depends on: ii konsole [x-terminal-emul 4:3.3.2-1 KDE X terminal emulator ii libx11-protocol-perl 0.53-2 Perl module for the X Window Syste ii openssh-client 1:4.1p1-6 Secure shell client, an rlogin/rsh ii perl-tk 1:800.025-2 Perl module providing the Tk graph ii xterm [x-terminal-emulat 4.3.0.dfsg.1-14 X terminal emulator clusterssh recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312476: (no subject)
Package: clusterssh Version: 3.13.1-1 Severity: normal I can confirm the above problem on my box. It appears both with [EMAIL PROTECTED] combinations used in /etc/clusters and when using 'Add Host' from the GUI menu. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages clusterssh depends on: ii konsole [x-terminal-emul 4:3.3.2-1 KDE X terminal emulator ii libx11-protocol-perl 0.53-2 Perl module for the X Window Syste ii perl-tk 1:800.025-2 Perl module providing the Tk graph ii ssh 1:4.1p1-3 Secure shell client and server (tr ii xterm [x-terminal-emulat 4.3.0.dfsg.1-14 X terminal emulator -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#312476: Found the source of the bug...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
... now if only I knew enough Perl to fix it. The offending lines are
these (starting line 543):
# see if we can find the hostname - if not, drop it
if(!gethost($_))
{
warn(WARNING: unknown host $_ - ignoring\n);
next;
}
The '!gethost($_)' of course chokes at something that is
'[EMAIL PROTECTED]', if you just strip everything up to and including the @,
the bug should be fixed. (as a workaround, I uncommented the 'next;' for
now)
Greetings,
Michel
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (MingW32) - GPGrelay v0.958
iD8DBQFCpu4C2Vs+MkscAyURAmj8AJ9GP+lwaEPF17MKscjEvsVLIHWXvACfUoAi
cIMhot+oNJXLsMi1mHnsIdo=
=wpxX
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#304615: asterisk-web-vmail: vmail.cgi can't access voicemail.conf by default
Package: asterisk-web-vmail Version: 1:1.0.7.dfsg.1-2 Severity: important By default, vmail.cgi gives the following error when trying to access a voice mailbox (after typing username and password): --- cut --- Software error: Bleh, no /etc/asterisk/voicemail.conf at /usr/lib/cgi-bin/asterisk/vmail.cgi line 96. --- cut --- (This is: trying to use it with Apache 1.3 by just installing the packages) To get it to work you either need to add www-data to the asterisk group or change the permissions of voicemail.conf like this: chgrp www-data /etc/asterisk/voicemail.conf That way, apache can access the config file and vmail.cgi works. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages asterisk-web-vmail depends on: ii apache [httpd-cgi]1.3.33-4 versatile, high-performance HTTP s ii apache2-mpm-prefork [httpd-cg 2.0.53-5 traditional model for Apache2 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#304615: asterisk-web-vmail: vmail.cgi can't accessvoicemail.conf by default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kilian Krause wrote: Hi Michel, Hello, Bleh, no /etc/asterisk/voicemail.conf at /usr/lib/cgi-bin/asterisk/vmail.cgi line 96. can you try dpkg --force-depends -P asterisk-config;apt-get --reinstall install asterisk-config please? I've no idea where this came from, but i do indeed see the same issue with my box. Having asterisk-config provide these files according to dpkg -L asterisk-config, but the dir being empty except for: -rw-r--r-- 1 root root 10345 Mar 21 11:23 indications.conf -rw-r--r-- 1 root root 2514 Mar 21 11:23 modem.conf -rw-r--r-- 1 root root 5020 Mar 21 11:23 queues.conf Do you reckon this is what you have too? No, in my case the file DID exist (the error message is misleading) but had the following permissions: - -rw-r- 1 asterisk asterisk 7000 Mar 21 12:23 voicemail.conf As a result, Apache (and thus the vmail.cgi script) couldn't access the file and returned the aforementioned error message. And do you reckon the above fixes the problem for you? Doing the reinstall of the package I now have: - -rw-r--r-- 1 root root 7000 Mar 21 12:23 voicemail.conf That does fix the problem (by making voicemail.conf world-readable) but at the same time it could be considered a security issue (voicemail.conf containing the vmail passwords, it shouldn't be world readable I guess). What I did instead was 'chgrp asterisk /etc/asterisk/voicemail.conf' which makes the file look as follows: - -rw-r- 1 asterisk www-data 7000 Mar 21 12:23 voicemail.conf Result: Asterisk can access the file and Apache can also get to it (through the www-data group). Alternatively you could leave ownership at asterisk.asterisk and instead add the user www-data to the asterisk group, granting it access to asterisk's files. Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) - GPGrelay v0.958 iD8DBQFCXmGt2Vs+MkscAyURAkmYAKDtMkOEitIRdicCcv85MINv2kGcTgCg9o+X oW6XEc2HQRuFsGnpLL5EJ3U= =1xYD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#304615: asterisk-web-vmail: vmail.cgi can't accessvoicemail.confby default
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kilian Krause wrote: No, in my case the file DID exist (the error message is misleading) but had the following permissions: - -rw-r- 1 asterisk asterisk 7000 Mar 21 12:23 voicemail.conf ok, in that case, the reply on pkg-voip with Tzafrir is the valid one. We need to propose to put vmail.cgi into suexec or have the apache in the asterisk group. Both of which should give the valid configuration. Does it work now that the permissions are correct? Yes, once I corrected the permissions, vmail.cgi works fine, at least as far as I can see. Maybe it will have trouble accessing the voice mails themselves later but I'm only starting to play with Asterisk right now so I don't have any yet. Greetings, Michel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (MingW32) - GPGrelay v0.958 iD8DBQFCXmcI2Vs+MkscAyURAsSgAJ9OOp8U+pQ653OjvoRYojv8F++fBACgm4/i Dc/CKdao0d/jmZwpSvxv3WQ= =bENO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
