Bug#994870: [Pkg-xen-devel] Bug#994870: Bug#994870: Bug#994870: Memory allocation problem for VM after xen security update
Hei hei, On Thu, Sep 30, 2021 at 01:13:54PM +0200, Hans van Kranenburg wrote: > Hi! > > On 9/30/21 12:45 AM, Andy Smith wrote: > > Hi Alex, > > > > On Thu, Sep 30, 2021 at 12:10:32AM +0200, Alexander Dahl wrote: > >> Am 22.09.21 um 20:54 schrieb Hans van Kranenburg: > >>> At this point I would really recommend to not wait for a fix to arrive > >>> which makes it start again, but change your VM to use a 64-bit kernel. > >> > >> How? > > > > This was answered in earlier comments on this bug; please see: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994870#15 > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994870#20 > > > > The brief summary is, "start out like a crossgrade, but only do the > > kernel". Very simple and quite safe. > > > > You haven't said how you boot your guest though (show us your > > /etc/xen/guest.cfg file). If it's pvgrub, that has a 32-bit and a > > 64-bit version so you'll need to change those as well. If it's > > pygrub you probably don't need to do anything, though pygrub has its > > own issues outside the scope of this bug. > > > >> FWIW, Debian 10 VMs with 32 bit running with PVH work fine. My important VM > >> is still Debian 9 however due to a software I can not simply upgrade. > > > > I've found PVH needs at least 4.19 guest kernel to work, which can > > be achieved in Debian 9 (stretch) today by using kernel from > > stretch-backports, so perhaps that is an option for you. > > You can certainly do that and then run PVH. This actually works. I'm running 4.19 i686 kernel in the stretch VM now with PVH, at least for the Debian stretch VM (I had to permanently disable some old OpenWRT VMs, where I get no updates anymore). Was a little tricky to install it, because I had to install that kernel without the vm being able to start, but it worked like this: - mount the root filesystem of the vm in the host, e.g. to /mnt - bind mount /dev, /sys to /mnt/dev and /mnt/sys - mount procfs to /mnt/proc - mount a tmpfs to /mnt/run and create /run/lock - chroot into /mnt - install the needed kernel with apt - leave chroot, umount the things from above - change domU config to PVH - when in grub, edit the cmdline and change root= if it was changed by update-grub (might have been changed to the mount point from the chroot) - in the now booted system, run update-grub again > Since stretch-backports is not used any more since stretch became > oldoldstable, new 4.19 backports kernels for Stretch are released > through the security updates channel. Be aware of this. > > https://lists.debian.org/debian-lts-announce/2020/08/msg00019.html > > Latest in stretch-backports (frozen) is 4.19.118, and stretch security > is now at 4.19.194. So double check you end up following the right one. Thanks for all your hints. I really have to migrate my virtual machines. :-/ Greets Alex -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL| (Jean-Luc Picard, quoting Judge Aaron Satie) signature.asc Description: PGP signature
Bug#994870: [Pkg-xen-devel] Bug#994870: Bug#994870: Memory allocation problem for VM after xen security update
Hello, Am 22.09.21 um 20:54 schrieb Hans van Kranenburg: Hi Ruediger, On 9/22/21 11:37 AM, H.-R. Oberhage wrote: Package: xen-system-amd64 Version: 4.14.3-1~deb11u1 After applying the buster security update to xen, my VM won't start any longer, complaining about a memory allocation error. Can you confirm that this is a virtual machine that tries to boot a 32-bit kernel as PV type? I can confirm this for three of my virtual machines. The error message you are seeing is not particularly helpful, but it is most likely related to this. The fact that with this package update 32-bit PV guests fail to start is indeed a regression problem, which is quite inconvenient for you, right now. And for me. :-/ At this point I would really recommend to not wait for a fix to arrive which makes it start again, but change your VM to use a 64-bit kernel. How? Let me know if you need help or run into problems while making this change. Running 32-bit PV at all is already 'on life support' upstream for quite a while now, and it also not under security support any more. Ack. FWIW, Debian 10 VMs with 32 bit running with PVH work fine. My important VM is still Debian 9 however due to a software I can not simply upgrade. In the long run, I'd suggest working towards having 64-bit guests in PVH mode, since that's one of the best options we have these days. Ack. If there's a reason you really cannot switch to a 64-bit kernel or move the functionality of this virtual machine to a new fully 64 bit system, switching the virtualization type from PV to HVM would also be an option. Thanks for your support. Greets Alex Switching back to the previous version 4.14.2+25-gb6a8c4f72d-2 lets the VM start (again,) normally. /var/log/libvirt/libxl/libxl-driver.log: 2021-09-21 14:01:44.645+: xc: panic: xc_dom_boot.c:120: xc_dom_boot_mem_init: can't allocate low memory for domain: Out of memory 2021-09-21 14:01:44.653+: libxl: libxl_dom.c:593:libxl__build_dom: xc_dom_boot_mem_init failed: Die Operation wird nicht unterstützt [means: the operation is not supported] 2021-09-21 14:01:44.662+: libxl: libxl_create.c:1576:domcreate_rebuild_done: Domain 1:cannot (re-)build domain: -3 The error is triggered, regardless if there was a boot-parameter "dom0_mem=1024M:max=2048M" set or not. /etc/xen/xl.conf was unaltered, i.e. 'autoballoon' was implicitely set to "auto". I am "on" Buster, kernel 5.10.0-8-amd64 (5.10.46-4), all relevant fixes included. Apologies for the inconvenience, Hans ___ Pkg-xen-devel mailing list pkg-xen-de...@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-xen-devel
Bug#944612: [Pkg-xen-devel] system still crashes with bullseye and kernel v5.3
Hello, On Wed, Dec 18, 2019 at 10:37:47PM +0100, Hans van Kranenburg wrote: > I expect the problem to be related to Linux and the hardware, and not > specifically Xen. Knowing if the same happens when just booting Linux > without Xen is valuable debugging info. However, I realize that it's > likely a bit complicated to, in that case, try triggering the problem by > generate the same workload that's now coming from the domUs. What I did in early 2020 was replacing the hardware. I threw out the 10 year old mainboard, cpu, and memory and put in something much more recent. Everything runs rock solid again since then. So you can close this report I guess, sorry for the noise. Greets Alex -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL| (Jean-Luc Picard, quoting Judge Aaron Satie) signature.asc Description: PGP signature
Bug#944612: system still crashes with bullseye and kernel v5.3
Hello there, meanwhile I'm running bullseye with kernel v5.3, but the problem persists and my Xen system is annoyingly unstable due to this bug. I attach some more logs from the last days and add the debian xen devel list in Cc. Maybe someone over there has an idea how to fix this. After all the log shows plenty of hints it could have something to do with Xen. Anyone care to help debug this? I have no idea where to start. Can kernel or xen generate coredumps one could analyze? Or is the log output the only thing? (If you look at the logs, the strange thing is the system does not crash and reboot immediately, but later after lots of errors with storage, but comes back fine after reboot.) Greets Alex [80412.164770] [ cut here ] [80412.164862] NETDEV WATCHDOG: enp1s0 (e1000e): transmit queue 0 timed out [80412.164947] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x248/0x250 [80412.164959] Modules linked in: nf_tables nfnetlink xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd crypto_simd cryptd glue_helper aes_x86_64 e [80412.164999] usb_common [80412.165079] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.3.0-2-amd64 #1 Debian 5.3.9-3 [80412.165088] Hardware name: Gigabyte Technology Co., Ltd. H55M-UD2H/H55M-UD2H, BIOS F11 08/20/2010 [80412.165099] RIP: e030:dev_watchdog+0x248/0x250 [80412.165106] Code: 85 c0 75 e5 eb 9f 4c 89 ef c6 05 22 66 a9 00 01 e8 cd 1e fb ff 44 89 e1 4c 89 ee 48 c7 c7 58 ab f0 81 48 89 c2 e8 06 87 a1 ff <0f> 0b eb 805 [80412.165124] RSP: e02b:c900400b4e70 EFLAGS: 00010282 [80412.165131] RAX: RBX: 888005d08200 RCX: [80412.165139] RDX: 88802c203098 RSI: c900400b4d8c RDI: 0004 [80412.165147] RBP: 888005dc445c R08: 88802bc00b68 R09: 88802bc00cb0 [80412.165155] R10: R11: 8204fc68 R12: [80412.165164] R13: 888005dc4000 R14: 888005dc4480 R15: 0001 [80412.165181] FS: 7f90e06e6740() GS:888031e4() knlGS: [80412.165190] CS: e030 DS: 002b ES: 002b CR0: 80050033 [80412.165198] CR2: 7f8a1104afc0 CR3: 287da000 CR4: 0660 [80412.165210] Call Trace: [80412.165217] [80412.165225] ? pfifo_fast_enqueue+0x150/0x150 [80412.165234] call_timer_fn+0x2d/0x130 [80412.165240] __run_timers.part.0+0x167/0x260 [80412.165249] ? handle_irq_event_percpu+0x72/0x80 [80412.165256] run_timer_softirq+0x26/0x50 [80412.165265] __do_softirq+0xe6/0x2e9 [80412.165272] irq_exit+0xa6/0xb0 [80412.165280] xen_evtchn_do_upcall+0x2c/0x40 [80412.165287] xen_do_hypervisor_callback+0x29/0x40 [80412.165294] [80412.165300] RIP: e030:xen_hypercall_sched_op+0xa/0x20 [80412.165307] Code: 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3c [80412.165325] RSP: e02b:c9004007fea8 EFLAGS: 0246 [80412.165331] RAX: RBX: 0001 RCX: 810013aa [80412.165339] RDX: 0dcbdc66 RSI: RDI: 0001 [80412.165347] RBP: 0001 R08: 4923528930b9 R09: [80412.165356] R10: 7ff0 R11: 0246 R12: 88802c22ee00 [80412.165364] R13: R14: R15: 88802c22ee00 [80412.165373] ? xen_hypercall_sched_op+0xa/0x20 [80412.165382] ? xen_safe_halt+0xc/0x20 [80412.165389] ? default_idle+0x1a/0x140 [80412.165398] ? do_idle+0x1fa/0x270 [80412.165404] ? cpu_startup_entry+0x19/0x20 [80412.165410] ? cpu_bringup_and_idle+0x6a/0x90 [80412.165418] ---[ end trace 2c4dfd0231d1cb4e ]--- [80412.165712] e1000e :01:00.0 enp1s0: Reset adapter unexpectedly [80412.166367] xenbr0: port 1(enp1s0.128) entered disabled state [80412.166476] xenbr1: port 1(enp1s0.389) entered disabled state [67573.237627] [ cut here ] [67573.237662] NETDEV WATCHDOG: enp1s0 (e1000e): transmit queue 0 timed out [67573.237693] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x248/0x250 [67573.237704] Modules linked in: tun nf_tables nfnetlink xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd crypto_simd cryptd glue_helper aes_x86e [67573.237806] usb_common [67573.237889] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.3.0-2-amd64 #1 Debian 5.3.9-3 [67573.237898] Hardware name: Gigabyte Technology Co., Ltd. H55M-UD2H/H55M-UD2H, BIOS F11 08/20/2010 [67573.237909] RIP: e030:dev_watchdog+0x248/0x250 [67573.237917] Code: 85 c0 75 e5 eb 9f 4c 89 ef c6 05 22 66 a9 00 01 e8 cd 1e fb ff 44 89 e1 4c 89 ee 48 c7 c7 58 ab f0 81 48 89 c2 e8 06 87 a1 ff <0f> 0b eb 805 [67573.237935] RSP: e02b:c900400b4e70 EFLAGS: 00010282 [67573.237941] RAX: RBX: 888005d24a00 RCX: 0006 [67573.237950] RDX: 0007 RSI: 0001 RDI: 888031e57680 [67573.237958] RBP: 88800582845c R08: 04f0 R09:
Bug#944612: Additional Log Files
Here the promised console logs. Hope that helps.
Greets
Alex
P.S.: sorry I messed up my initial From: address, please use this one.
[251782.115527] [ cut here ]
[251782.115569] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
[251782.115622] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x20d/0x220
[251782.115647] Modules linked in: devlink nf_tables nfnetlink xen_netback xen_blkback xen_gntdev xc
[251782.115751] hid_generic usbhid hid crc32c_intel ahci libahci i2c_i801 lpc_ich firewire_ohci fi]
[251782.115785] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.19.0-5-amd64 #1 Debian 4.19.37-5
[251782.115794] Hardware name: Gigabyte Technology Co., Ltd. H55M-UD2H/H55M-UD2H, BIOS F11 08/20/200
[251782.115807] RIP: e030:dev_watchdog+0x20d/0x220
[251782.115814] Code: 00 49 63 4e e0 eb 92 4c 89 e7 c6 05 31 62 ae 00 01 e8 97 c0 fc ff 89 d9 4c 896
[251782.115833] RSP: e02b:888031e03e98 EFLAGS: 00010282
[251782.115840] RAX: RBX: RCX: 0006
[251782.115849] RDX: 0007 RSI: 0001 RDI: 888031e166b0
[251782.115858] RBP: 88800557045c R08: 053e R09: 0720072007200774
[251782.115867] R10: 0775076f07200764 R11: 0765076d07690774 R12: 88800557
[251782.115876] R13: R14: 888005570480 R15: 0001
[251782.115895] FS: 7f75789c2800() GS:888031e0() knlGS:
[251782.115904] CS: e033 DS: ES: CR0: 80050033
[251782.115912] CR2: 7fff023e4128 CR3: 291a CR4: 0660
[251782.115926] Call Trace:
[251782.115933]
[251782.115941] ? pfifo_fast_enqueue+0x110/0x110
[251782.115952] call_timer_fn+0x2b/0x130
[251782.115959] run_timer_softirq+0x3d1/0x410
[251782.115967] ? handle_irq_event_percpu+0x6d/0x80
[251782.115976] ? handle_percpu_irq+0x40/0x60
[251782.115984] __do_softirq+0xde/0x2d8
[251782.115993] irq_exit+0xba/0xc0
[251782.116002] xen_evtchn_do_upcall+0x2c/0x40
[251782.116012] xen_do_hypervisor_callback+0x29/0x40
[251782.116019]
[251782.116026] RIP: e030:xen_hypercall_sched_op+0xa/0x20
[251782.116033] Code: 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc ccc
[251782.116051] RSP: e02b:82003e70 EFLAGS: 0246
[251782.116058] RAX: RBX: RCX: 810013aa
[251782.116067] RDX: 32d7ebca RSI: RDI: 0001
[251782.116076] RBP: R08: 2318fb4b R09:
[251782.116085] R10: 7ff0 R11: 0246 R12:
[251782.116094] R13: R14: R15:
[251782.116104] ? xen_hypercall_sched_op+0xa/0x20
[251782.116113] ? xen_safe_halt+0xc/0x20
[251782.116120] ? default_idle+0x1c/0x140
[251782.116127] ? do_idle+0x1f1/0x280
[251782.116133] ? cpu_startup_entry+0x6f/0x80
[251782.116141] ? start_kernel+0x50c/0x52c
[251782.116149] ? default_get_nmi_reason+0x10/0x10
[251782.116158] ? xen_start_kernel+0x587/0x592
[251782.116165] ---[ end trace 911e57ed83519137 ]---
[251804.672131] ata10.00: exception Emask 0x0 SAct 0x1f80 SErr 0x0 action 0x6 frozen
[251804.672182] ata10.00: failed command: WRITE FPDMA QUEUED
[251804.672192] ata10.00: cmd 61/10:38:68:99:58/00:00:4e:00:00/40 tag 7 ncq dma 8192 out
[251804.672192] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[251804.672209] ata10.00: status: { DRDY }
[251804.672215] ata10.00: failed command: WRITE FPDMA QUEUED
[251804.672223] ata10.00: cmd 61/08:40:90:99:58/00:00:4e:00:00/40 tag 8 ncq dma 4096 out
[251804.672223] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[251804.672274] ata10.00: status: { DRDY }
[251804.672280] ata10.00: failed command: WRITE FPDMA QUEUED
[251804.672289] ata10.00: cmd 61/10:48:b0:99:58/00:00:4e:00:00/40 tag 9 ncq dma 8192 out
[251804.672289] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[251804.672305] ata10.00: status: { DRDY }
[251804.672311] ata10.00: failed command: WRITE FPDMA QUEUED
[251804.672319] ata10.00: cmd 61/08:50:e8:99:58/00:00:4e:00:00/40 tag 10 ncq dma 4096 out
[251804.672319] res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[251804.672336] ata10.00: status: { DRDY }
[251804.672342] ata10.00: failed command: WRITE FPDMA QUEUED
[251804.672351] ata10.00: cmd 61/08:58:08:33:5a/00:00:4e:00:00/40 tag 11 ncq dma 4096 out
[251804.672351] res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[251804.672367] ata10.00: status: { DRDY }
[251804.672373] ata10.00: failed command: WRITE FPDMA QUEUED
[251804.672382] ata10.00: cmd 61/08:60:b8:a7:5c/00:00:4e:00:00/40 tag 12 ncq dma 4096 out
[251804.672382] res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[251804.672398] ata10.00: status: { DRDY }
[251804.672407] ata10: hard resetting link
[â¦
[313562.171136] xen-blkback: Scheduled work from
Bug#944618: duplicate
Sorry, I messed up. This is a duplicate of #944612. Please close this one. Greets Alex signature.asc Description: OpenPGP digital signature
Bug#944612: linux-image-5.2.0-3-amd64: netdev watchdog triggers on xen with different nics leading to different failures
Package: src:linux Version: 5.2.17-1 Severity: important Dear Maintainer, my computer crashes after random times of running (few hours to several days) with kernels from Debian 8, 9, or 10 (but not 7) when running as xen dom0, always with netdev watchdog timeout on transmit queue. It is a home server running debian since 2009, rock solid until Debian 7 with kernel 3.16.x, random crashes with kernels 4.9, 4.19, and 5.2, always with xen. Different network adapters, different actual failures afterwards. Sometimes only the network adapter resets, sometimes sata devices fail, but operate normal again after reboot. memtest does not show any errors. Usually I have to reboot this host and restart the virtual machines running on it. I dist-upgraded from Debian 7 to 8, and collected console output over the last year for Debian 9 and (not yet released) with different kernel versions. The first line of the log after "cut here" is always the same (although with different network adapters): NETDEV WATCHDOG: *** (***): transmit queue 0 timed out The call trace always shows things like xen and irq, e.g.: [19565.293440] [ cut here ] [19565.293599] NETDEV WATCHDOG: enp1s0 (e1000e): transmit queue 0 timed out [19565.293627] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:448 dev_watchdog+0x253/0x260 [19565.293637] Modules linked in: nf_tables nfnetlink xen_netback xen_blkback xen_gntdev xen_evtchn xenfs xen_privcmd crypto_simd cryptd glue_helper aes_x86_64 e [19565.293675] usb_common [19565.293755] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.2.0-3-amd64 #1 Debian 5.2.17-1 [19565.293764] Hardware name: Gigabyte Technology Co., Ltd. H55M-UD2H/H55M-UD2H, BIOS F11 08/20/2010 [19565.293775] RIP: e030:dev_watchdog+0x253/0x260 [19565.293782] Code: 48 85 c0 75 e4 eb 9d 4c 89 ef c6 05 07 a6 aa 00 01 e8 11 3f fb ff 89 d9 4c 89 ee 48 c7 c7 70 31 f0 81 48 89 c2 e8 57 da a2 ff <0f> 0b e9 7c6 [19565.293800] RSP: e02b:c90040003e90 EFLAGS: 00010286 [19565.293807] RAX: RBX: RCX: 0006 [19565.293815] RDX: 0007 RSI: 0001 RDI: 888031e17680 [19565.293823] RBP: 88800550445c R08: 04d1 R09: 072007740775076f [19565.293831] R10: 072007640765076d R11: 0769077407200730 R12: 88800546f680 [19565.293840] R13: 888005504000 R14: 888005504480 R15: 0001 [19565.293858] FS: 7f0c08afb740() GS:888031e0() knlGS: [19565.293867] CS: e030 DS: ES: CR0: 80050033 [19565.293874] CR2: 7fbdde9ec3e8 CR3: 049f CR4: 0660 [19565.293886] Call Trace: [19565.293893] [19565.293900] ? pfifo_fast_enqueue+0x140/0x140 [19565.293908] call_timer_fn+0x2d/0x130 [19565.293914] run_timer_softirq+0x401/0x440 [19565.293923] ? handle_irq_event_percpu+0x6d/0x80 [19565.293931] ? handle_percpu_irq+0x40/0x60 [19565.293939] __do_softirq+0xde/0x2f7 [19565.293947] irq_exit+0xab/0xb0 [19565.293956] xen_evtchn_do_upcall+0x2c/0x40 [19565.293963] xen_do_hypervisor_callback+0x29/0x40 [19565.293970] [19565.293976] RIP: e030:xen_hypercall_sched_op+0xa/0x20 [19565.293983] Code: 51 41 53 b8 1c 00 00 00 0f 05 41 5b 59 c3 cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc 51 41 53 b8 1d 00 00 00 0f 05 <41> 5b 59 c3c [19565.294000] RSP: e02b:82003e90 EFLAGS: 0246 [19565.294007] RAX: RBX: RCX: 810013aa [19565.294015] RDX: 029058ea RSI: RDI: 0001 [19565.294023] RBP: R08: 13f85928 R09: [19565.294031] R10: 7ff0 R11: 0246 R12: [19565.294039] R13: R14: R15: [19565.294049] ? xen_hypercall_sched_op+0xa/0x20 [19565.294058] ? xen_safe_halt+0xc/0x20 [19565.294065] ? default_idle+0x1c/0x140 [19565.294073] ? do_idle+0x1f1/0x280 [19565.294079] ? cpu_startup_entry+0x19/0x20 [19565.294086] ? start_kernel+0x4ed/0x50b [19565.294093] ? default_get_nmi_reason+0x10/0x10 [19565.294100] ? xen_start_kernel+0x585/0x58f [19565.294107] ---[ end trace e694416b458ba149 ]--- Although this is annoying and I considered buying new hardware, I'm confident this could be solved, if someone assists me. I offer to test new kernels and could also compile those by myself. I will attach my logfiles in further responses to this report. Kind regards Alex -- Package-specific info: ** Version: Linux version 5.2.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-22)) #1 SMP Debian 5.2.17-1 (2019-09-26) ** Command line: placeholder root=/dev/mapper/heaven-heaven_root64 ro console=tty0 console=hvc0 memtest ip=192.168.243.70::192.168.243.1:255.255.255.0:heaven.internal.home.lespocky.de:enp3s0 ** Not tainted ** Kernel log: [ 868.524964] xenbr3: port 2(vif1.0) entered blocking state [ 868.524989] xenbr3: port 2(vif1.0) entered disabled
Bug#913481: confirm
Hello Axel, On Thu, Aug 08, 2019 at 10:17:44PM +0200, Axel Beckert wrote: > I though never ran into this myself (and wasn't aware of that comment > in mkswap). I also never came across a Raspbian using F2FS so far > although the idea sounds quite obvious. FTR, this is no configuration Raspbian comes with by default. You have to backup the default content (ext4?), install the necessary f2fs-tools, reformat the root partition with f2fs, update your /etc/fstab and the fix all upcoming problems by yourself. ;-) I liked the idea and wanted to play with it, especially because I saw SD-cards die and F2FS promises to be gentle to the card and thus delay that problem. Greets Alex -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL| (Jean-Luc Picard, quoting Judge Aaron Satie) signature.asc Description: PGP signature
Bug#913481: confirm
Hello, I can confirm this problem for Raspbian 10 (buster, after upgrading from 9, stretch) on a F2FS rootfs. Deleting /var/swap, creating it with dd from /dev/zero and manually mkswap it, solves the problem, the service starts again then. swapon failed before with the aforementioned error in kernellog: [Thu Aug 8 21:39:30 2019] swapon: swapfile has holes I suspect the problem being the use of 'fallocate' and 'f2fs'. man mkswap(8) states this: Note that a swap file must not contain any holes. Using cp(1) to create the file is not acceptable. Neither is use of fallocate(1) on file systems that support preallocated files, such as XFS or ext4, or on copy-on-write filesystems like btrfs. It is recommended to use dd(1) and /dev/zero in these cases. Please read notes from swapon(8) before adding a swap file to copy-on-write filesystems. Hope that helps to fix the package?! Kind regards Alex signature.asc Description: OpenPGP digital signature
Bug#923907: Acknowledgement (webext-browserpass: No toolbar icon in Firefox 60)
I'm a little emberassed, but after reboot the extension works now in Firefox. No idea, was has happened, but I guess this can be closed. o.O -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL| (Jean-Luc Picard, quoting Judge Aaron Satie) signature.asc Description: PGP signature
Bug#923907: webext-browserpass: No toolbar icon in Firefox 60
Package: webext-browserpass Version: 2.0.22-2 Severity: important Dear Maintainer, while the browser plugin from this package works fine with Chromium, it does not with Firefox. It is listed in the installed addons, but there's no toolbar icon nor menu entry to use it. It is also not possible to drag such an icon to the toolbar from the customization menu (what's called "Anpassen …" in German locale). pass itself with Git works fine, qtpass also does, so I assume some problem with the Firefox part of this webext? Greets Alex -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages webext-browserpass depends on: ii libc6 2.28-7 Versions of packages webext-browserpass recommends: ii chromium 72.0.3626.109-1 ii firefox-esr 60.5.1esr-1 webext-browserpass suggests no packages. -- no debconf information
Bug#912381: xen-utils-4.11: /usr/lib/xen-4.11/bin/pygrub is missing after upgrade from xen-utils-4.8
Hei hei, On Wed, 31 Oct 2018 19:16:11 +0100 Hans van Kranenburg wrote: > An alternative that might help you now might be to switch to pvgrub2? This is an alternative for Debian virtual machines. At least I use pygrub to boot other distributions, which don't have pvgrub. So thanks for fixing pygrub! :-) Greets Alex
Bug#912975: xen-hypervisor-4.8-amd64: Dom0 crashes randomly without logs on Debian Stretch with Xen 4.8.4
Hei hei, On Fri, Feb 22, 2019 at 07:24:11PM +0100, Hans van Kranenburg wrote: > The current state of this bug does not really allow anyone other than > yourself to cause it to progress. FWIW, I also have problems with Xen and stretch on amd64. Since upgrading from jessie I get random crashes, which means the system hangs and I only can do a hard powercycle. I'm currently reorganizing the partitions to get enough space for a debug kernel on the rootfs, otherwise the stacktraces are probably not of big help? (I would have upgraded to buster already, but pygrub is broken there, so maybe we get stretch fixed until then.) Greets Alex -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL| (Jean-Luc Picard, quoting Judge Aaron Satie) signature.asc Description: PGP signature
Bug#541544: [PATCH] ash: reset tokpushback before prompting while parsing heredoc
Hei hei, I just stumbled over an old entry in the Debian Bug tracker. Am Dienstag, 20. November 2018, 21:56:13 CET schrieb Ron Yorston: > Christoph Schulz wrote: > >I could not reproduce the problem with dash, neither with git dash nor > >with older versions (0.5.8, 0.5.9.1, 0.5.10.2, to name a few). > >Something must be handled differently. But I haven't compared busybox > >ash and dash sources thoroughly either. > > The same issue is present in dash and has been discussed in a mailing > list thread starting here: > >https://www.spinics.net/lists/dash/msg01652.html By chance, is that old Debian Bug here referencing the same problem? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541544 Maybe someone could tell Debian, then? o.O Alex
Bug#903767: Bug#903800: 4.9.110-1 Xen PV boot workaround
Hello, I can confirm both the boot loop with 4.9.110-1 and that the boot loop is gone with 4.9.110-3 from stretch-proposed-updates. HTH & Greets Alex -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL| (Jean-Luc Picard, quoting Judge Aaron Satie) signature.asc Description: PGP signature
Bug#803744: Info received (Still not fixed in Raspbian GNU/Linux 9 (stretch))
Hei hei, meanwhile I found Debian bug report #883026 which addresses the same underlying problem. I'm not familiar with managing those reports, maybe someone can set this as duplicate? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883026 Greets Alex signature.asc Description: PGP signature
Bug#803744: Still not fixed in Raspbian GNU/Linux 9 (stretch)
Hei hei, I can confirm that behaviour for Raspbian GNU/Linux 9 (stretch), quote from syslog: Jul 20 17:17:04 darcy systemd-fsck[96]: fsck.f2fs: invalid option -- 'y' Jul 20 17:17:04 darcy systemd-fsck[96]: #011Error: Unknown option ? Jul 20 17:17:04 darcy systemd-fsck[96]: Usage: fsck.f2fs [options] device Jul 20 17:17:04 darcy systemd-fsck[96]: [options]: Jul 20 17:17:04 darcy systemd-fsck[96]: -a check/fix potential corruption, reported by f2fs Jul 20 17:17:04 darcy systemd-fsck[96]: -d debug level [default:0] Jul 20 17:17:04 darcy systemd-fsck[96]: -f check/fix entire partition Jul 20 17:17:04 darcy systemd-fsck[96]: -p preen mode [default:0 the same as -a [0|1]] Jul 20 17:17:04 darcy systemd-fsck[96]: -t show directory tree [-d -1] If you have any hints on how to solve that, I would happily test it. Greets Alex -- /"\ ASCII RIBBON | »With the first link, the chain is forged. The first \ / CAMPAIGN | speech censured, the first thought forbidden, the X AGAINST | first freedom denied, chains us all irrevocably.« / \ HTML MAIL| (Jean-Luc Picard, quoting Judge Aaron Satie) signature.asc Description: PGP signature
Bug#221616: arpwatch behaviour inlogical wrt to flipflop/new station
Package: arpwatch Version: 2.1a15-2+b1 Followup-For: Bug #221616 Dear Maintainer, sorry, I missed this info in my last mail, should have used reportbug in the first place. O:-) Greets Alex -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages arpwatch depends on: ii adduser 3.115 ii libc6 2.24-11+deb9u1 ii libpcap0.8 1.8.1-3 arpwatch recommends no packages. arpwatch suggests no packages. -- no debconf information
Bug#221616: arpwatch: new station reports for known mac addresses
Hei hei, I can confirm for arpwatch on Debian 9 (stretch). There's a Windows 7 laptop on my network, which is frequently used in other networks. After "returning home" it still has the old IP address before getting a new one from my DHCP server. arpwatch reports this as "new station", although the mac address is known. The database fills up with such entries (mac addr last part replaced with xx): root@falbala /var/lib/arpwatch # grep 00:23:14:xx:xx:xx arp.dat 00:23:14:xx:xx:xx 172.19.25.165 1459790929 eth0 00:23:14:xx:xx:xx 172.19.12.103 1499872037 eth0 00:23:14:xx:xx:xx 172.19.28.241 1515699236 eth0 00:23:14:xx:xx:xx 192.168.1.2 1499200486 eth0 00:23:14:xx:xx:xx 192.168.243.162 1516984428 furball eth0 00:23:14:xx:xx:xx 192.168.1.8 1496190353 eth0 00:23:14:xx:xx:xx 192.168.1.7 1497056388 eth0 00:23:14:xx:xx:xx 192.168.1.9 1501110083 eth0 00:23:14:xx:xx:xx 192.168.1.4 1516731353 eth0 00:23:14:xx:xx:xx 192.168.2.116 1516980534 eth0 00:23:14:xx:xx:xx 10.182.63.163 1471649481 furball eth0 00:23:14:xx:xx:xx 10.182.63.162 1489622622 furball eth0 00:23:14:xx:xx:xx 169.254.145.38 1516935943 eth0 This is what the man page says: new station The ethernet address has not been seen before. In fact the ethernet address has seen before. I could better ignore those messages if I could remember this one mac address (see #527251) or maybe someone would like to fix this package? O:-) Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 *** signature.asc Description: PGP signature
Bug#534912: IMAP folder names having a dot (.) treated incorrectly
Package: mutt
Version: 1.7.2-1
Followup-For: Bug #534912
Dear Maintainer,
this bug is still not solved in stretch. Trying to open a folder named
'Archiv/Lists/ptxdist.2017' and get this error:
Can't open mailbox Archiv/Lists/ptxdist/2017: no such mailbox
Haven't tried the workaround, though.
Greets
Alex
-- Package-specific info:
NeoMutt 20170113 (1.7.2)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: Linux 4.9.0-3-686-pae (i686)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet
Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/6/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-2'
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-6 --program-prefix=i686-linux-gnu- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-i386/jre
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-i386
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-i386
--with-arch-directory=i386 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--with-target-system-z
lib --enable-objc-gc=auto --enable-targets=all --enable-multiarch
--with-arch-32=i686 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic --enable-checking=release --build=i686-linux-gnu
--host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 6.3.0 20161229 (Debian 6.3.0-2)
Configure options: '--build=i686-linux-gnu' '--prefix=/usr'
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man'
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var'
'--disable-silent-rules' '--libdir=\${prefix}/lib/i386-linux-gnu'
'--libexecdir=\${prefix}/lib/i386-linux-gnu' '--disable-maintainer-mode'
'--disable-dependency-tracking' '--with-mailpath=/var/mail'
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache'
'--enable-gpgme' '--enable-imap' '--enable-smtp' '--enable-pop'
'--enable-sidebar' '--enable-nntp' '--enable-notmuch' '--disable-fmemopen'
'--with-curses' '--with-gnutls' '--with-gss' '--with-idn' '--with-mixmaster'
'--with-sasl' '--without-gdbm' '--without-bdb' '--without-qdbm'
'--with-tokyocabinet' 'build_alias=i686-linux-gnu' 'CFLAGS=-g -O2
-fdebug-prefix-map=/build/mutt-7oKzXl/mutt-1.7.2=. -fstack-protector-strong
-Wformat -Werror=format-security' 'LDFLAGS=-Wl,-z,relro -Wl,-z,now'
'CPPFLAGS=-Wdate-time -D_FORTIFY
_SOURCE=2'
Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2
-fdebug-prefix-map=/build/mutt-7oKzXl/mutt-1.7.2=. -fstack-protector-strong
-Wformat -Werror=format-security -fno-delete-null-pointer-checks
Compile options:
+CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME
+DEBUG +DL_STANDALONE +ENABLE_NLS -EXACT_ADDRESS -HOMESPOOL -LOCALES_HACK
-SUN_ATTACHMENT +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET +HAVE_FUTIMENS
+HAVE_GETADDRINFO +HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET
+HAVE_LANGINFO_YESEXPR +HAVE_LIBIDN +HAVE_META +HAVE_REGCOMP +HAVE_RESIZETERM
+HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_WC_FUNCS +ICONV_NONTRANS
+USE_COMPRESSED +USE_DOTLOCK +USE_FCNTL -USE_FLOCK -USE_FMEMOPEN -USE_GNU_REGEX
+USE_GSS +USE_HCACHE +USE_IMAP +USE_NOTMUCH +USE_NNTP +USE_POP +USE_SASL
+USE_SETGID +USE_SIDEBAR +USE_SMTP +USE_SSL_GNUTLS -USE_SSL_OPENSSL
-DOMAIN
MIXMASTER="mixmaster"
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
patch-attach-headers-color-neomutt
patch-compose-to-sender-neomutt
patch-compress-neomutt
patch-cond-date-neomutt
patch-encrypt-to-self-neomutt
patch-fmemopen-neomutt
patch-forgotten-attachments-neomutt
patch-forwref-neomutt
patch-ifdef-neomutt
patch-index-color-neomutt
patch-initials-neomutt
patch-keywords-neomutt
patch-kyoto-neomutt
patch-limit-current-thread-neomutt
patch-lmdb-neomutt
patch-multiple-fcc-neomutt
patch-nested-if-neomutt
patch-new-mail-neomutt
patch-nntp-neomutt
patch-notmuch-neomutt
patch-progress-neomutt
patch-quasi-delete-neomutt
patch-reply-with-xorig-neomutt
patch-sensible-browser-neomutt
patch-sidebar-neomutt
patch-skip-quoted-neomutt
patch-status-color-neomutt
patch-timeout-neomutt
patch-tls-sni-neomutt
Bug#869903: regression: putting an hostname in authorized_keys from="" field does not work anymore in stretch
Hei hei, On Thu, Jul 27, 2017 at 10:27:28AM -0400, Simon Deziel wrote: > The UseDNS directive was switched to "no" in OpenSSH 6.8 [1]: > > * sshd(8): UseDNS now defaults to 'no'. Configurations that match >against the client host name (via sshd_config or authorized_keys) >may need to re-enable it or convert to matching against addresses. Well you're right. If I set this to 'yes' in sshd_confing everything works again. This is somehow documented in `man 5 sshd_config` but not in the authorized_keys docs. :-/ So thanks for the hint, this can be closed then. *blush* Sorry for the noise. Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: C28E E6B9 0263 95CF 8FAF 08FA 34AD CD00 7221 5CC6 *** signature.asc Description: PGP signature
Bug#869903: regression: putting an hostname in authorized_keys from="" field does not work anymore in stretch
Package: openssh-server Version: 1:7.4p1-10+deb9u1 Severity: normal Dear Maintainer, I used the 'from' field in authorized_keys with an hostname (fqdn) on Debian 8 (jessie), which worked fine (openssh-server 1:6.7p1-5+deb8u3). After upgrading the server to stretch, this does not work anymore. Putting an IP address in this field works however. This also does not work with current openssh-server in sid (1:7.5p1-5). In every case it was a hostname correctly resolvable by DNS, forward and backwards to one IPv4 address. Client has still been on jessie in both cases. The log message on the ssh server when failing is more or less misleading: Jul 27 13:39:16 susan sshd[9562]: Authentication tried for alex with correct key but not from a permitted host (host=192.168.243.98, ip=192.168.243.98). Greets Alex -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 4.9.0-3-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages openssh-server depends on: ii adduser3.115 ii debconf [debconf-2.0] 1.5.61 ii dpkg 1.18.24 ii init-system-helpers1.48 ii libaudit1 1:2.6.7-2 ii libc6 2.24-11+deb9u1 ii libcomerr2 1.43.4-2 ii libgssapi-krb5-2 1.15-1 ii libkrb5-3 1.15-1 ii libpam-modules 1.1.8-3.6 ii libpam-runtime 1.1.8-3.6 ii libpam0g 1.1.8-3.6 ii libselinux12.6-3+b1 ii libssl1.0.21.0.2l-2 ii libsystemd0232-25+deb9u1 ii libwrap0 7.6.q-26 ii lsb-base 9.20161125 ii openssh-client 1:7.4p1-10+deb9u1 ii openssh-sftp-server1:7.4p1-10+deb9u1 ii procps 2:3.3.12-3 ii ucf3.0036 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages openssh-server recommends: ii libpam-systemd 232-25+deb9u1 ii ncurses-term6.0+20161126-1 ii xauth 1:1.0.9-1+b2 Versions of packages openssh-server suggests: ii molly-guard 0.6.4 pn monkeysphere pn rssh pn ssh-askpass pn ufw -- debconf information: ssh/new_config: true * ssh/vulnerable_host_keys: ssh/encrypted_host_key_but_no_keygen: * ssh/use_old_init_script: true openssh-server/permit-root-login: true ssh/disable_cr_auth: false
Bug#843200: prosody: Please provide 0.9.11
Package: prosody Version: 0.9.10-1 Severity: wishlist Tags: upstream Dear Maintainer, upstream released 0.9.11 containing several bugfixes. Especially #648 is annoying in our setup here. See the release announcement: https://prosody.im/doc/release/0.9.11 Thanks and greets Alex -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages prosody depends on: ii adduser 3.115 ii libc6 2.24-5 ii libidn111.33-1 ii libssl1.0.2 1.0.2j-1 ii lua-expat [lua5.1-expat]1.3.0-3 ii lua-filesystem [lua5.1-filesystem] 1.6.3-1 ii lua-sec [lua5.1-sec]0.6-1 ii lua-socket [lua5.1-socket] 3.0~rc1+git+321c0c9-1 ii lua5.1 5.1.5-8.1+b1 ii ssl-cert1.0.38 Versions of packages prosody recommends: ii lua-event [lua5.1-event] 0.4.3-2 Versions of packages prosody suggests: pn lua-dbi-mysql pn lua-dbi-postgresql ii lua-dbi-sqlite3 0.5.hg5ba1dd988961-3 ii lua-zlib0.2+git+1+9622739-2 -- Configuration Files: /etc/prosody/conf.avail/example.com.cfg.lua [Errno 13] Keine Berechtigung: u'/etc/prosody/conf.avail/example.com.cfg.lua' /etc/prosody/conf.avail/localhost.cfg.lua [Errno 13] Keine Berechtigung: u'/etc/prosody/conf.avail/localhost.cfg.lua' /etc/prosody/prosody.cfg.lua [Errno 13] Keine Berechtigung: u'/etc/prosody/prosody.cfg.lua' -- no debconf information pgpyHzE6sz1JB.pgp Description: PGP signature
Bug#743998: also affects MySQL
Hei hei, FWIW, when using prosody with MySQL I have the very same problem. Workaround is logging in after a reboot and restarting prosody. *sigh* Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
Bug#798509: owncloud-client: 100% CPU load all the time
Package: owncloud-client Version: 1.7.0~beta1+really1.6.4+dfsg-1 Severity: important Tags: upstream Dear Maintainer, after upgrade from Wheezy to Jessie on my Samsung NC10 Netbook (Intel Atom CPU, i386) owncloud-client uses the whole CPU all the time making the whole system disturbingly slow. My owncloud server runs also on Debian Jessie and the problem occurs in the local network with very fast access to the server as well as abroad. owncloud folder has less than 4 GB space used, so it's still quite small I guess. I do not have this problem with x86-64 machines. This may be related to the following upstream bug, which was also spotted in different Ubuntu versions: https://github.com/owncloud/client/issues/2485 or maybe to some other bug also reported for Ubuntu [1]. Debian testing already has owncloud-client 2.0 depending on Qt5 so I did not try to use those packages, there's nothing in backports, so I decided to file this bug because I consider the package unusable on old/slow machines if it eats up all the CPU. I'm willing to support with tests or debugging, if somebody tells me how. Greets Alex [1] https://launchpad.net/ubuntu/+source/owncloud-client/+bugs -- System Information: Debian Release: 8.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages owncloud-client depends on: ii libc6 2.19-18 ii libgcc1 1:4.9.2-10 ii libowncloudsync0 1.7.0~beta1+really1.6.4+dfsg-1 ii libqt4-dbus 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-network4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-sql-sqlite 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqt4-xml4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtcore44:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libqtgui4 4:4.8.6+git64-g5dc8b2b+dfsg-3+deb8u1 ii libstdc++64.9.2-10 ii owncloud-client-l10n 1.7.0~beta1+really1.6.4+dfsg-1 owncloud-client recommends no packages. owncloud-client suggests no packages. -- no debconf information
Bug#758057: confirm
Hei hei, On a de locale machine with active systemd I get this output: lcd4linux (0.11.0~svn1200-2.1+b1) wird eingerichtet ... Job for lcd4linux.service failed. See 'systemctl status lcd4linux.service' and 'journalctl -xn' for details. invoke-rc.d: initscript lcd4linux, action start failed. dpkg: Fehler beim Bearbeiten des Paketes lcd4linux (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück Fehler traten auf beim Bearbeiten von: lcd4linux So it seems there must be a /etc/lcd4linux.conf … just copying over the sample from /usr/share/doc/lcd4linux does not work, you have to edit it and then fix access rights before you can successfully start it. In my opinion the package should install fine from scratch. Letting the user configure it so aptitude/dpkg does not have it as C / unconfigured anymore is not what packages usually do. Don't try to start an unconfigured daemon automatically, which will not start with the default config. I'm not sure what Debian policies say here, but I guess providing an always running default config, so it could always start right away, could be a solution. HTH Greets Alex signature.asc Description: OpenPGP digital signature
Bug#748247: additional findings
Hei hei, I ran into this again on jessie and investigated a little. This is what I found out: the file /etc/logcheck/ignore.d.server/ssmtp belongs to the package ssmtp, not to logcheck-database. The code actually sending the message matched against is in function 'int ssmtp(char *argv[])' somewhere near line 1689 of ssmtp.c: log_event(LOG_INFO, Sent mail for %s (%s) uid=%d username=%s outbytes=%d, from_strip(uad), buf, uid, pw-pw_name, outbytes); The part which does not match is the one in braces, and this 'buf' is filled some lines before with: (void)smtp_okay(sock, buf); This seems to be actually a response from the SMTP server and probably depends on the SMTP server where sSMTP drops the mail, so it could be any SMTP out there. I'm not familiar with different SMTP implementations and what the possible output could be, so I can not make a good suggestion what to match here. HTH Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761808: owncloud: lighttpd example conf suggests wrong alias path
Package: owncloud Version: 7.0.2+dfsg-1 Severity: minor Dear Maintainer, the file /usr/share/doc/owncloud/examples/lighttpd/owncloud.conf contains the following line: alias.url += ( /owncloud/ = /var/lib/owncloud/ ) This will not work, because the application itself is in /usr/share/owncloud at least like it's shipped at the moment. Furthermore I would suggest to remove the trailing slashes of the alias definition to avoid 404 if user just calls http://example.com/owncloud instead of http://example.com/owncloud/ so this works: alias.url += ( /owncloud = /usr/share/owncloud ) HTH Greets Alex -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages owncloud depends on: ii fonts-font-awesome 4.1.0~dfsg-1 ii fonts-liberation 1.07.4-1 ii fonts-linuxlibertine 5.3.0-2 ii fonts-lohit-deva 2.5.3-1 ii fonts-sil-gentium-basic 1.1-7 ii fonts-wqy-microhei 0.2.0-beta-2 ii libjs-chosen 0.9.11-2 ii libjs-dojo-dojox 1.10.0+dfsg-1 ii libjs-jcrop 0.9.12+dfsg-1 ii libjs-jquery-minicolors 1.2.1-1 ii libjs-jquery-mousewheel 10-1 ii libjs-jquery-timepicker 1.2-1 ii libjs-pdf1.0.712+dfsg-1 ii libphp-phpmailer 5.2.8+dfsg-1 ii lighttpd [httpd] 1.4.35-3 ii owncloud-doc 0~20140824-1 ii php-assetic 1.1.2-1 ii php-doctrine-dbal2.4.2-4 ii php-getid3 1.9.8-1 ii php-opencloud1.10.0-2 ii php-patchwork-utf8 1.1.25-1 ii php-pear 5.6.0+dfsg-1 ii php-pimple 1.1.1-1 ii php-sabre-dav1.8.10-1 ii php-seclib 0.3.7-1 ii php-symfony-classloader 2.3.6-1 ii php-symfony-console 2.3.1+dfsg-1 ii php-symfony-routing 2.0.19-1 ii php5 5.6.0+dfsg-1 ii php5-gd 5.6.0+dfsg-1 ii php5-json1.3.6-1 ii php5-mysql 5.6.0+dfsg-1 ii zendframework1.12.7-0.1 Versions of packages owncloud recommends: ii libav-tools 6:11~beta1-2 pn libreoffice none ii php-aws-sdk 2.6.15+comp-1 ii php-crypt-blowfish1.1.0~RC2-3 ii php-dropbox 1.0.0-2 ii php-google-api-php-client 0.6.7-2 ii php5-apcu 4.0.6-1 ii php5-cli 5.6.0+dfsg-1 ii php5-curl 5.6.0+dfsg-1 ii php5-imagick 3.1.2-1.1+b1 pn php5-intl none pn php5-ldap none ii php5-mcrypt 5.6.0+dfsg-1 ii smbclient 2:4.1.11+dfsg-1 ii ssmtp [mail-transport-agent] 2.64-8 Versions of packages owncloud suggests: pn libapache2-mod-xsendfile none pn mysql-server | virtual-mysql-server | postgresql none -- 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#748247: logcheck-database: wrong ssmtp ignore regex triggers mail every hour
Package: logcheck-database
Version: 1.3.16
Severity: normal
Dear Maintainer,
I installed logcheck-database together with ssmtp. The regex for sSMTP
does not match the ssmtp output in syslog, so this
% sudo cat /etc/logcheck/ignore.d.server/ssmtp
^\w{3} [ :0-9]{11} [._[:alnum:]-]+ sSMTP\[[0-9]+\]: Sent mail for .* \([0-9]+
[0-9.]+ Bye\) uid=[0-9]+ username=[\._[:alnum:]-]+ outbytes=[0-9]+$
does not match this
% sudo grep -i ssmtp /var/log/syslog :(
May 15 14:18:50 troubadix sSMTP[1742]: Sent mail for r...@example.com (221
idefix.example.com closing connection) uid=0 username=root outbytes=994
May 15 15:07:57 troubadix sSMTP[4196]: Sent mail for r...@example.com (221
idefix.example.com closing connection) uid=0 username=root outbytes=5206
May 15 15:32:39 troubadix sSMTP[2502]: Sent mail for logch...@example.com (221
idefix.example.com closing connection) uid=104 username=logcheck outbytes=41970
May 15 15:37:54 troubadix sSMTP[2620]: Sent mail for a...@example.com (221
idefix.example.com closing connection) uid=2001 username=alex outbytes=400
May 15 16:02:26 troubadix sSMTP[4241]: Sent mail for logch...@example.com (221
idefix.example.com closing connection) uid=104 username=logcheck outbytes=1422
(my domain replaced with example.com)
The mailserver ssmtp delivers to is not Debian but eisfair-2 running
package 'mail' which is actually exim.
Anyway, this leads to mails every hour because logcheck sending out
mail leads to an entry in syslog which is not ignored leading to the
next mail of logcheck. This affects current Debian 7.5 (Wheezy) too.
Greets
Alex
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 3.13-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
-- Configuration Files:
/etc/logcheck/cracking.d/kernel [Errno 13] Permission denied:
u'/etc/logcheck/cracking.d/kernel'
/etc/logcheck/cracking.d/rlogind [Errno 13] Permission denied:
u'/etc/logcheck/cracking.d/rlogind'
/etc/logcheck/cracking.d/rsh [Errno 13] Permission denied:
u'/etc/logcheck/cracking.d/rsh'
/etc/logcheck/cracking.d/smartd [Errno 13] Permission denied:
u'/etc/logcheck/cracking.d/smartd'
/etc/logcheck/cracking.d/tftpd [Errno 13] Permission denied:
u'/etc/logcheck/cracking.d/tftpd'
/etc/logcheck/cracking.d/uucico [Errno 13] Permission denied:
u'/etc/logcheck/cracking.d/uucico'
/etc/logcheck/ignore.d.paranoid/bind [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/bind'
/etc/logcheck/ignore.d.paranoid/cron [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/cron'
/etc/logcheck/ignore.d.paranoid/incron [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/incron'
/etc/logcheck/ignore.d.paranoid/logcheck [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/logcheck'
/etc/logcheck/ignore.d.paranoid/postfix [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/postfix'
/etc/logcheck/ignore.d.paranoid/ppp [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/ppp'
/etc/logcheck/ignore.d.paranoid/pureftp [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/pureftp'
/etc/logcheck/ignore.d.paranoid/qpopper [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/qpopper'
/etc/logcheck/ignore.d.paranoid/squid [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/squid'
/etc/logcheck/ignore.d.paranoid/ssh [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/ssh'
/etc/logcheck/ignore.d.paranoid/stunnel [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/stunnel'
/etc/logcheck/ignore.d.paranoid/sysklogd [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/sysklogd'
/etc/logcheck/ignore.d.paranoid/telnetd [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/telnetd'
/etc/logcheck/ignore.d.paranoid/tripwire [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/tripwire'
/etc/logcheck/ignore.d.paranoid/usb [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.paranoid/usb'
/etc/logcheck/ignore.d.server/acpid [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.server/acpid'
/etc/logcheck/ignore.d.server/amandad [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.server/amandad'
/etc/logcheck/ignore.d.server/amavisd-new [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.server/amavisd-new'
/etc/logcheck/ignore.d.server/anacron [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.server/anacron'
/etc/logcheck/ignore.d.server/anon-proxy [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.server/anon-proxy'
/etc/logcheck/ignore.d.server/apache [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.server/apache'
/etc/logcheck/ignore.d.server/apcupsd [Errno 13] Permission denied:
u'/etc/logcheck/ignore.d.server/apcupsd'
/etc/logcheck/ignore.d.server/arpwatch
Bug#740509: confirm
I can confirm this for jessie and package version 10.0+ds1-1. This is rather annoying, because at the moment the FreeBSD 9 kernel is removed on upgrade and you have no running network afterwards making reinstall older packages over network impossible. I run the 32 bit version in VMware player on Debian Linux. Kernel (dmesg) says device em0 is present and it shows the correct MAC address. Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742275: Info received (Patch queued upstream)
Hei hei, upstream applied my change manually to 2.x branch, but the change itself should be okay. See https://github.com/zfsnap/zfsnap/pull/43 for details. Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** pgpi20eZIE6S1.pgp Description: PGP signature
Bug#742275: Patch queued upstream
Hei hei, I made a pull request upstream for the change I made: https://github.com/graudeejs/zfSnap/pull/43 However: upstream seems to rewrite the code for a new major release and reorganized the code structure so the patch applies to v1.11.1 but not to master which is in some pre 2.0.0 state at the moment. Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742275: zfsnap: unusable on kfreebsd architectures (OS not supported)
Package: zfsnap Version: 1.11.1-2 Severity: important Tags: upstream Dear Maintainer, zfSnap returns the following on kfreebsd-amd64 architecture on every single call (using --help just to show the effect): # zfSnap --help FATAL: Your OS isn't supported This is due to a check on the output of `uname` in the beginning of the script which does not know about GNU/kFreeBSD. This makes it completely unusable on Debian GNU/kFreeBSD. Tested on both kfreebsd-amd64 and kfreebsd-i386 which return the same string mentioned above. Greets Alex -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 10.0-1-amd64 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages zfsnap depends on: ii zfsutils 9.2-4 zfsnap recommends no packages. zfsnap 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#742275: zfsnap: unusable on kfreebsd architectures (OS not supported)
Hei hie, Am 2014-03-21 15:52, schrieb John Goerzen: Just to be clear, what precisely is the output of uname on your system? GNU/kFreeBSD If you modify the script to accept that, then does it appear to work? I didn't test this yet. I'm unfamiliar with zfSnap and wanted to try if it could fit my needs. What is the proper value for ESED on your system? (FreeBSD is using 'sed -E', Linux is using 'sed -r') Not sure, installed is the package sed 4.2.2-4 which is GNU sed: root@kleopatra ~ # sed --version sed (GNU sed) 4.2.2 Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html. This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Written by Jay Fenlason, Tom Lord, Ken Pizzini, and Paolo Bonzini. GNU-sed-Homepage: http://www.gnu.org/software/sed/. Allgemeine Hilfe zu GNU-Software: http://www.gnu.org/gethelp/. E-mail bug reports to: bug-...@gnu.org. Be sure to include the word ``sed'' somewhere in the ``Subject:'' field. On a real FreeBSD 10.0 I get no version information from sed: alex@hydrogen ~ % sed --version sed: illegal option -- - usage: sed script [-Ealn] [-i extension] [file ...] sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...] So I guess Debian GNU/kFreeBSD should use `sed -r`. Some short tests with the uname added next to the Linux one on my machine seem to work, but as I said: I don't know zfSnap yet, so I can't estimate if everything works as it should. HTH Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704983: git-daemon-sysvinit: needless option --home when creating system user with --no-create-home
Package: git-daemon-sysvinit Version: 1:1.7.10.4-2 Severity: minor Dear Maintainer, when installing I get these: Vormals nicht ausgewähltes Paket git-daemon-sysvinit wird gewählt. (Lese Datenbank ... 30169 Dateien und Verzeichnisse sind derzeit installiert.) Entpacken von git-daemon-sysvinit (aus .../git-daemon-sysvinit_1%3a1.7.10.4-2_all.deb) ... git-daemon-sysvinit (1:1.7.10.4-2) wird eingerichtet ... Warnung: Auf das von Ihnen angegebene Home-Verzeichnis /nonexistent kann nicht zugegriffen werden: Datei oder Verzeichnis nicht gefunden Lege Systembenutzer »gitdaemon« (UID 104) an ... Lege neuen Benutzer »gitdaemon« (UID 104) mit Gruppe »nogroup« an ... Erstelle Home-Verzeichnis »/nonexistent« nicht. The warning is caused by the paramater --home=/nonexistent when calling add-user in postinst. This is needless because add-user is correctly called with --no-create-home anyway. Removing the --home option from the call would remove the warning with same functionality. HTH Greets -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-daemon-sysvinit depends on: ii adduser 3.113+nmu3 ii git 1:1.7.10.4-2 git-daemon-sysvinit recommends no packages. git-daemon-sysvinit suggests no packages. -- no debconf information pgpJ_Au8ynrNx.pgp Description: PGP signature
Bug#704985: git-daemon-sysvinit: GIT_DAEMON_BASE_PATH missing in /etc/default/git-daemon
Package: git-daemon-sysvinit Version: 1:1.7.10.4-2 Severity: minor Dear Maintainer, when changing GIT_DAEMON_DIRECTORY in the /etc/default/git-daemon coming with the package to e.g. /srv/repos/git the git-daemon is still called with --base-path=/var/cache because GIT_DAEMON_BASE_PATH has the default value from /etc/init.d/git-daemon but is not included in /etc/default/git-daemon which leads to a path not found error. I could fix this by adding GIT_DAEMON_BASE_PATH='/srv/repos' to my /etc/default/git-daemon so I guess it would be nice to deliver a better template or default /etc/default/git-daemon containg GIT_DAEMON_BASE_PATH or improve /usr/share/doc/git-daemon/README* HTH Greets Alex -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git-daemon-sysvinit depends on: ii adduser 3.113+nmu3 ii git 1:1.7.10.4-2 git-daemon-sysvinit recommends no packages. git-daemon-sysvinit suggests no packages. -- no debconf information pgpejKng8tNeK.pgp Description: PGP signature
Bug#691851: using logrotate hint
according to the error message it would be possible to add a line like this to /etc/logrotate.d/lastfmsubmitd and fix this as well: su root lastfm not tested however. Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699681: apper: Accepting updated packages fails because Apper downgrades to current version
Package: apper Version: 0.7.2-5 Followup-For: Bug #699681 Hei hei, I can confirm this for multiarch (this system) and a non multiarch 32bit x86 (virtual) machine at work, both at wheezy. I have apticron installed in parallel on this machine here, which already downloads packages in the background. This behaviour of apper is very annoying and was introduced not until a few days ago in wheezy. HTH Greets Alex -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apper depends on: ii apper-data 0.7.2-5 ii kde-runtime 4:4.8.4-2 ii libc62.13-37 ii libdebconf-kde0 0.2-2 ii libgcc1 1:4.7.2-5 ii libkcmutils4 4:4.8.4-4 ii libkdecore5 4:4.8.4-4 ii libkdeui54:4.8.4-4 ii libkemoticons4 4:4.8.4-4 ii libkidletime44:4.8.4-4 ii libkio5 4:4.8.4-4 ii libkprintutils4 4:4.8.4-4 ii libkutils4 4:4.8.4-4 ii libkworkspace4abi1 4:4.8.4-5 ii libpackagekit-qt2-2 0.7.6-2 ii libqt4-dbus 4:4.8.2+dfsg-10 ii libqt4-network 4:4.8.2+dfsg-10 ii libqt4-sql 4:4.8.2+dfsg-10 ii libqt4-svg 4:4.8.2+dfsg-10 ii libqt4-xml 4:4.8.2+dfsg-10 ii libqt4-xmlpatterns 4:4.8.2+dfsg-10 ii libqtcore4 4:4.8.2+dfsg-10 ii libqtgui44:4.8.2+dfsg-10 ii libsolid44:4.8.4-4 ii libstdc++6 4.7.2-5 ii packagekit 0.7.6-2 ii policykit-1-gnome0.105-2 ii polkit-kde-1 0.99.0-3 Versions of packages apper recommends: ii app-install-data 2012.06.16.1 Versions of packages apper suggests: pn apper-appsetup none ii debconf-kde-helper 0.2-2 ii software-properties-kde 0.82.7.1debian1 -- 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#533831: duplicate kde bug?
I found another entry in the KDE bug database covering the same topic: https://bugs.kde.org/show_bug.cgi?id=256255 HTH Greets signature.asc Description: OpenPGP digital signature
Bug#515626: mpd: confirmed on Pentium 133
Package: mpd Version: 0.15.8-1+b1 Severity: normal I can confirm this behaviour on a Pentium 133 MHz (no MMX) with 192 MB RAM. Kernel and packages are up to date from Debian Squeeze 2010-03-03. Skips still appear with nice value of -3 on all mpd processes. CPU load is between 27% and 69% viewed in htop but usually around 45% to 50%. Setting nice level to -6 doesn't work either. Soundcard is a Soundblaster AWE 64 ISA card and mp3 files are on a hard disk encrypted with dm-crypt/Luks. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.32-trunk-486 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpd depends on: ii adduser3.112 add and remove users and groups ii libao2 0.8.8-5 Cross Platform Audio Output Librar ii libasound2 1.0.22-2 shared library for ALSA applicatio ii libaudiofile0 0.2.6-8 Open-source version of SGI's audio ii libavcodec52 5:0.5+svn20100208-0.1 library to encode decode multimedi ii libavformat52 5:0.5+svn20100208-0.1 ffmpeg file format library ii libavutil494:0.5+svn20090706-6 ffmpeg utility library ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libcue11.3.0-1 CUE Sheet Parser Library ii libcurl3-gnutls7.19.7-1 Multi-protocol file transfer libra ii libfaad2 2.7-4 freeware Advanced Audio Decoder - ii libflac8 1.2.1-2+b1Free Lossless Audio Codec - runtim ii libgcc11:4.4.2-9 GCC support library ii libglib2.0-0 2.22.4-1 The GLib library of C routines ii libid3tag0 0.15.1b-10ID3 tag reading library from the M ii libjack0 0.118+svn3796-2 JACK Audio Connection Kit (librari ii libmad00.15.1b-5 MPEG audio decoder library ii libmms00.4-2 MMS stream protocol library - shar ii libmpcdec6 2:0.1~r453-1 MusePack decoder - library ii libogg01.1.4~dfsg-2 Ogg bitstream library ii libpulse0 0.9.21-1 PulseAudio client libraries ii libresid-builder0c 2.1.1-8 SID chip emulation class based on ii libsamplerate0 0.1.7-3 Audio sample rate conversion libra ii libshout3 2.2.2-5+b1MP3/Ogg Vorbis broadcast streaming ii libsidplay22.1.1-8 SID (MOS 6581) emulation library ii libsqlite3-0 3.6.22-1 SQLite 3 shared library ii libstdc++6 4.4.2-9 The GNU Standard C++ Library v3 ii libvorbis0a1.2.3-3 The Vorbis General Audio Compressi ii libvorbisenc2 1.2.3-3 The Vorbis General Audio Compressi ii libvorbisfile3 1.2.3-3 The Vorbis General Audio Compressi ii libwavpack14.60.1-1 an audio codec (lossy and lossless mpd recommends no packages. Versions of packages mpd suggests: pn avahi-daemon none (no description available) pn icecast2 none (no description available) ii lastmp [mpd-client] 1.0.5-1.1 MPD client for lastfmsubmitd ii mpc [mpd-client] 0.19-2 A command-line tool to interface M ii ncmpc [mpd-client]0.16.1-1 ncurses-based audio player pn pulseaudionone (no description available) -- 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#546772: confirmed
confirmed. however, the program doesn't seem to stop. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#526188: problem seems to be solved
Hi, when cleaning my mail inbox I noticed this open bug report. I don't have 100% CPU load with anymore since several weeks now. I think the update of libqca2-plugin-gnupg to version 2.0.0~beta3-1 solved this issue. I think the bug can be closed. Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** signature.asc Description: OpenPGP digital signature
Bug#520387: caff: option 'mail' in .caffrc is ignored
Hi, If you can give it a quick try, that would be great. Sorry for the late answer. Meanwhile I have signing-party 1.1.1-1 installed and the bug is closed, but I wanted to let you know: the problem doesn't occur here anymore. :-) Thanks and greets Alex signature.asc Description: OpenPGP digital signature
Bug#526188: psi: CPU load on 100% and no connection possible when GPG key set
Package: psi Version: 0.12.1-1 Severity: normal Since last week Psi is unusable when I set a GnuPG key in my user account. When starting the CPU load goes to 100% and doesn't fall anymore until I close Psi. There's no connection established at all and chatting is impossible, although option dialogs are usable without problems. If I set the account to use no GnuPG key Psi works fine (despite of bug #525765). Greets Alex -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages psi depends on: ii libaspell150.60.6-1 GNU Aspell spell-checker runtime l ii libc6 2.9-8 GNU C Library: Shared libraries ii libgcc11:4.3.3-8 GCC support library ii libqca22.0.0-4 libraries for the Qt Cryptographic ii libqca2-plugin-ossl0.1~20070904-3QCA OSSL plugin for libqca2 ii libqt4-dbus4.5.1-1 Qt 4 D-Bus module ii libqt4-network 4.5.1-1 Qt 4 network module ii libqt4-qt3support 4.5.1-1 Qt 3 compatibility library for Qt ii libqt4-xml 4.5.1-1 Qt 4 XML module ii libqtcore4 4.5.1-1 Qt 4 core module ii libqtgui4 4.5.1-1 Qt 4 GUI module ii libstdc++6 4.3.3-8 The GNU Standard C++ Library v3 ii libx11-6 2:1.2.1-1 X11 client-side library ii libxss11:1.1.3-1 X11 Screen Saver extension library ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime Versions of packages psi recommends: ii sox 14.2.0-2 Swiss army knife of sound processi Versions of packages psi suggests: ii libqca2-plugin-gnupg 0.1~20070904-2 QCA gnupg plugin for libqca2 ii psi-translations 1.9Translations for psi ii xdg-utils 1.0.2-6.1 desktop integration utilities from -- no debconf information signature.asc Description: Digital signature
Bug#520387: caff: option 'mail' in .caffrc is ignored
Package: signing-party
Version: 1.1-2
Severity: normal
I added the following line to my ~/.caffrc
$CONFIG{'mail'} = 'yes';
According to manpage this should have the same effect as calling caff
with '--mail yes'. Commandline option works as intended, but if I set
this option in .caffrc it is ignored and 'ask-yes' is active so I have
to hit enter on every single mail caff wants to send. I had a short look
in the source and I think the line I added to .caffrc is correct,
because the option has exactly this name and the possible values are
'yes', 'ask-yes', 'ask-no' and 'no'. However setting this in .caffrc
doesn't work for me.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i586)
Kernel: Linux 2.6.22
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages signing-party depends on:
ii gnupg 1.4.9-4GNU privacy guard - a free PGP rep
ii libc6 2.9-4 GNU C Library: Shared libraries
ii libclass-methodmaker-perl 2.15-1 perl module for creating generic m
ii libgnupg-interface-perl 0.36-1 Perl interface to GnuPG
ii libmailtools-perl 2.04-1 Manipulate email in perl programs
ii libmime-tools-perl5.427-2Perl5 modules for MIME-compliant m
ii libterm-readkey-perl 2.30-4 A perl module for simple terminal
ii libtext-template-perl 1.44-1.2 Text::Template perl module
ii perl 5.10.0-19 Larry Wall's Practical Extraction
Versions of packages signing-party recommends:
ii dialog1.1-20080819-1 Displays user-friendly dialog boxe
ii libgd-gd2-perl1:2.39-2 Perl module wrapper for libgd - gd
ii libpaper-utils1.1.23+nmu1library for handling paper charact
ii libtext-iconv-perl1.7-1+b1 converts between character sets in
ii ssmtp [mail-transport-age 2.62-3 extremely simple MTA to get mail o
ii whiptail 0.52.2-11.3Displays user-friendly dialog boxe
Versions of packages signing-party suggests:
pn imagemagick | graphicsmagick- none (no description available)
ii mutt 1.5.18-6 text-based mailreader supporting M
pn wipe none (no description available)
-- 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#500068: lcd4linux: should start after MPd
Package: lcd4linux Version: 0.10.1~rc2-2 Severity: normal lcd4linux tries to connect to MPd at startup and fails. This is because MPd is started later in the boot process so lcd4linux is not able to connect yet. If I manually restart lcd4linux later when MPd is already running everything works fine. I suggest to start lcd4linux after MPd. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i586) Kernel: Linux 2.6.22 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lcd4linux depends on: ii libc6 2.7-13GNU C Library: Shared libraries ii libgd2-noxpm 2.0.36~rc1~dfsg-3 GD Graphics Library version 2 (wit ii libmpd00.15.0-3 High-level client library for acce ii libmysqlclient15off5.0.51a-15MySQL database client library ii libncurses55.6+20080830-1shared libraries for terminal hand ii libusb-0.1-4 2:0.1.12-12 userspace USB programming library ii libx11-6 2:1.1.4-2 X11 client-side library ii python2.4 2.4.5-5 An interactive high-level object-o lcd4linux recommends no packages. lcd4linux suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#466075: more information about corrupted database
In the case mpd fails to start (this is not always the case) the database is always corrupted in a similar way. There is a single keyword in which one character is shifted 16 characters forward. I can open the database (tag_cache) in a text editor, correct this single wrong character and successfully start mpd then. I give some examples of wrong database keywords: Corrupted Must be - --- Gunre Genre Qlbum Album DqteDate I had several other corrupted keywords all with this one wrong character shifted forward. This seems to be one Bit flipped. e-u is 65h-75h is 01100101b-01110101b I double checked RAM with Memtest86+ -- no error. No other application has problems on this machine. I guessed the error appeared always at the same line or even same byte position in the database, but that's not the case. However it's in the same region somewhere in the middle of the database between lines 20 and 30 and always in the keywords not in the values. I forgot to mention, this is with Debian Lenny and package version 0.13.1-3 and the same machine as with my initial report. It occurs not as often as with the previous version but I guess still every fourth or fifth time I boot the machine. signature.asc Description: OpenPGP digital signature
