Bug#967538: ipwatchd-gnotify: depends on deprecated GTK 2
Hello Bastian, yes, ipwatchd-gnotify can be removed from Debian. Please let me know if my cooperation is needed. Regards, Jaroslav On Mon, 14 Aug 2023 at 18:30, Bastian Germann wrote: > Hi Jaroslav, > > Would it be okay for you to remove ipwatchd-gnotify from Debian? > > Thanks for your consideration, > Bastian >
Bug#986821: freecad: Garbled menu makes freecad unusable
Hello, I found this bug report trying to troubleshoot the same issue - for me, FreeCAD UI is completely garbled, all menu items, all icons, all other UI elements are larger than the space allocated for them, resulting in "create new empty document" icon being cut after 90% of its length, "open document" after 60% etc. making 4th icon barely visible and rest completely invisible. Essentially, the UI element graphics is being drawn into different positions compared to where those elements are actually placed in the UI. Since the symptoms were the same for me - no issue for clean slate system user - I tried the strace approach. But even after filtering things that are the same out, I was unsuccessful. However, using the QT_SCALE_FACTOR=1 QT_AUTO_SCREEN_SCALE_FACTOR=0 variables made the thing work and eventually I figured out the problem is caused by my monitor DPI settings (xfce4-settings-manager -> Appearance -> Fonts -> Custom DPI settings) I have this value set to 80. Tried changing it to "default" 96 and that fixed the issue for me. I would say this is a FreeCAD bug though, according to my x.org log, my monitor does have 80DPI: (++) RADEON(0): DPI set to (80, 80) (The monitor has 59.6x33.6cm screen dimensions with 1920x1080 resolution, which also amounts to 80DPI.) As far as I know (was told once by some develeper), developers tend to assume that every monitor has 96DPI and write programs accordingly. Might be the case here.
Bug#979460: xfce4-panel: Multiple problems in Status Tray plugin (Xfce 4.16)
Hello, I am affected by this bug as well and I think as more people migrate to Bullseye, they will be affected too. For me, the system tray is losing icons. I usually have 3 programs supposed to be shown in there: kalarm, psi and kteatime. Sometimes all 3 of them are shown for a while but sometimes the tray doesn't even pick them up and shows only two (kalarm being the one affected the most and not showing most of the time.) After some time of using the PC more icons gradually disappear, psi being the second most affected one. Since those programs are supposed to be minimized to tray most of the time, the only way to access them after this happens is restarting them (luckily, both programs detect their previous instance and make it appear - if that wasn't the case, only way to gain access to the program would be killing it from console and restarting it altogether) When this happens, the following can be observed in system tray settings: right click panel - menu item "Panel" - "Panel Preferences..." - "Items" tab - double click "Status Tray Plugin". In the "Known Items" area, there are items for each application and those affected by this show light grey icon with darker gray exclamation mark in a triangle instead of their own icon - not sure how relevant this is though. There is also a bug that affects kteatime. When it shows an "tea is ready" event, its icon changes to a light bulb and never reverts back, making it non-usable since there is no possibility to distinguish last event from a new one. This is reported at https://gitlab.xfce.org/xfce/xfce4-panel/-/issues/340 . I am not sure if this bug is related to the previous one. I believe - if anyone has the time - that this bug should get some attention because, in my opinion, it has significant impact on usability of Xfce as a whole. If there are some patches to test and the xfce4-panel package can be rebuilt from source using apt-get source and dpkg-buildpackage, I should be able to provide testing and feedback. Thanks
Bug#991702: kate: Regression in Ruby indentation in Bullseye
Package: kate Version: 4:20.12.2-1 Severity: normal X-Debbugs-Cc: jaros...@thinline.cz Dear Maintainer, after upgrading from Buster to Bullseye, Kate text editor's behaviour regarding Ruby indentation changed with significant regression The bug can be reproduced like this (correct behaviour first): - open new document, switch its indentation to Ruby - type if v =~ /re/i - cursor correctly indents one tab to the right. All subsequent lines are indented as well until you type "end", which is immediatelly and automatically de-indented: if v =~ /re/i statement end - same example but with the regexp being case-sensitive, ie. no "i" at the end if v =~ /re/ - cursor indents two tabs to the right, my guess would be the indenter doesn't consider that regexp to be complete (expecting at least one more letter). Next line is de-indented to a single tab indentation, which is correct, but indentation in most of the code after such block does not work correctly. Final code looks like this: if v =~ /re/ statement statement end The following is more elaborate example of indentation errors caused by this regression. All indentation shown is done by the editor, nothing is adjusted manually: statement =~ /re/ begin if v =~ /re/ statement statement end rescue statement end The following is the correct behaviour observed when the regexp is case-insensitive (again, no manual indentation adjustment): statement =~ /re/i begin if v =~ /re/i statement statement end rescue statement end I tried to find out the code responsible for this. Kate version in Buster had a package kate-data containing indentation scripts, notably /usr/share/kde4/apps/katepart/script/indentation/ruby.js But I am unsure if that was actually in use. Trying to put that file (and its dependencies found by looking at require statements in the script) into ~/.local/share/katepart5/script/indentation as documented in https://docs.kde.org/stable5/en/kate/katepart/dev-scripting.html broke Ruby indentation altogether (no automated indentation was taking place) I haven't been able to figure out where the indentation-related code is stored now, so I wasn't able to try to fix this myself. Any help or advice would be appreciated Thanks -- System Information: Debian Release: 11.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-7-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages kate depends on: ii kate5-data 4:20.12.2-1 ii kio 5.78.0-5 ii ktexteditor-katepart 5.78.0-3 ii libc62.31-13 ii libkf5bookmarks5 5.78.0-2 ii libkf5completion55.78.0-3 ii libkf5configcore55.78.0-4 ii libkf5configgui5 5.78.0-4 ii libkf5configwidgets5 5.78.0-2 ii libkf5coreaddons55.78.0-4 ii libkf5crash5 5.78.0-3 ii libkf5dbusaddons55.78.0-2 ii libkf5guiaddons5 5.78.0-3 ii libkf5i18n5 5.78.0-2 ii libkf5iconthemes55.78.0-2 ii libkf5jobwidgets55.78.0-2 ii libkf5kiocore5 5.78.0-5 ii libkf5kiofilewidgets55.78.0-5 ii libkf5kiogui55.78.0-5 ii libkf5kiowidgets55.78.0-5 ii libkf5newstuff5 5.78.0-4 ii libkf5parts5 5.78.0-3 ii libkf5plasma55.78.0-3 ii libkf5service-bin5.78.0-2 ii libkf5service5 5.78.0-2 ii libkf5syntaxhighlighting55.78.0-2 ii libkf5texteditor55.78.0-3 ii libkf5textwidgets5 5.78.0-2 ii libkf5threadweaver5 5.78.0-2 ii libkf5wallet-bin 5.78.0-2 ii libkf5wallet55.78.0-2 ii libkf5widgetsaddons5 5.78.0-2 ii libkf5windowsystem5 5.78.0-2 ii libkf5xmlgui55.78.0-2 ii libkuserfeedbackcore11.0.0-3 ii libkuserfeedbackwidgets1 1.0.0-3 ii libqt5core5a 5.15.2+dfsg-9 ii libqt5dbus5 5.15.2+dfsg-9 ii libqt5gui5 5.15.2+dfsg-9 ii libqt5sql5 5.15.2+dfsg-9 ii libqt5widgets5
Bug#987598: linux-image-5.10.0-6-amd64: no longer accounting guest CPU time in /proc/stat
Hello, looks like this is fixed in current kernel version in Bullseye. Thanks for your help.
Bug#987599: linux-image-5.10.0-6-amd64: regression, diskstats show unrealistic values
Package: src:linux Version: 5.10.28-1 Severity: normal Hello, after upgrading some of our servers to Debian testing I noticed that their reported disk utilization increased significantly. Since there was no other indication of them being under load and since I had a prior knowledge of similar bug reported few years ago, I investigated the source of the data and discovered that the values shown are inflated. Steps to reproduce: Using FIO I tried to find out some kind of maximum IOPS the drives (two SSDs in RAID1) can perform: [global] name=fio-rand-write filename=fio-rand-write rw=randwrite bs=4K direct=1 numjobs=1 time_based=1 runtime=900 [file1] size=1G ioengine=libaio iodepth=16 FIO output while running was showing about 30k IOPS: Jobs: 1 (f=1): [w(1)][0.8%][w=116MiB/s][w=29.7k IOPS][eta 14m:53s] Drive utilization was 100% as expected, 10th column (time spent doing I/O in milliseconds) was increasing by 1000 each second # while sleep 1 ; do cat /sys/block/sda/stat ; done 4845 2532 264597 1489 5509215 237957 56950332 268397 0 334780 274445118470 161240352 382317304 734 4845 2532 264597 1489 5529013 237960 57108732 269200 0 335780 275249118470 161240352 382317306 734 4845 2532 264597 1489 5548918 237960 57267972 270008 0 336784 276056118470 161240352 382317306 734 4845 2532 264597 1489 5568868 237960 57427572 270815 0 337788 276863118470 161240352 382317306 734 After that I added IOPS limit to FIO configuration (limit max reading, writing, discarding IOPS): rate_iops=100,100,100 This took effect in performance reported by FIO Jobs: 1 (f=1), 0-100 IOPS: [w(1)][1.2%][w=400KiB/s][w=100 IOPS][eta 14m:49s] And increments in time spent doing I/O dropped to 400ms each second. # while sleep 1 ; do cat /sys/block/sda/stat ; done 5067 2602 265364 1511 6587946 239193 65578139 314735 0 428856 320973119310 161241296 384720712 879 5067 2602 265364 1511 6588046 239193 65578939 314742 0 429256 320981119310 161241296 384720712 879 5067 2602 265364 1511 6588146 239193 65579739 314750 0 429656 320989119310 161241296 384720712 879 I tried to increase IOPS limit by factor of 2.5 to 250 and at that point the drive load went back to full (ie. time spent doing I/O in milliseconds incrementing by 1000 each second.) Both of those values seem way off, it isn't likely that an SSD would need 4ms to write a small chunk of data. That's rotating drive level of performance. All drives I tested showed the same behaviour, regardless of them being single drives or part of an MD array. Drives are two different brands. This is a regression from Debian Stable kernel, where insignificant load (from the perspective of an SSD) didn't increase the "time spent doing I/O" counter at all. Which is IMO the sensible thing to do as you usually don't care if the drive reports zero load when the actual load is slightly more than zero. Current (testing) kernel version on the other hand causes "drives fully loaded" alerts when the drives are in reality almost idle. Meaning of the 10th column is taken from https://www.kernel.org/doc/Documentation/iostats.txt This issue is similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927184 , but unlike that bug - which could be worked around by choosing mq-deadline scheduler - it affects mq-deadline as well. This is why I reported this separately as a regression. (I removed PCI information included by reportbug since I don't think this is a hardware-related issue. If needed, I can provide it.) -- Package-specific info: ** Version: Linux version 5.10.0-6-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-6-amd64 root=UUID=bc4aa9fd-9c63-445e-aeae-2147798879f4 ro amd_iommu=on intel_iommu=on net.ifnames=0 ** Not tainted ** Kernel log: [4.185348] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [4.191508] PTP clock support registered [4.194579] ccp :42:00.1: SEV API:0.24 build:3 [4.264204] checking generic (b600 30) vs hw (b600 100) [4.264207] fb0: switching to astdrmfb from EFI VGA [4.268024] Console: switching to colour dummy device 80x25 [4.268247] ast :c4:00.0: [drm] P2A bridge disabled, using default configuration [4.268250] ast :c4:00.0: [drm] AST 2500 detected [4.268257] ast :c4:00.0: [drm] Analog VGA only [4.268259] ast :c4:00.0: [drm] dram MCLK=800 Mhz type=1 bus_width=16 [
Bug#987598: linux-image-5.10.0-6-amd64: no longer accounting guest CPU time in /proc/stat
Package: src:linux Version: 5.10.28-1 Severity: normal Hello, after upgrading some of our Qemu/KVM host servers to Debian testing I noticed that their CPU load changed from "user" to "system" (observed via Prometheus and Grafana.) After quick digging I found that the new kernel is no longer counting "guest" time and 9th column in /proc/stat stays 0 at all times. This is a regression from Debian stable. Steps to reproduce: chpst -u :4:4:115 \ /usr/bin/kvm -m 8192 -smp 4 -nodefaults \ -device virtio-scsi-pci,id=scsi \ -drive file=/mnt/grub.img,if=none,cache=none,format=raw,discard=on,id=disk-lvm-4 \ -device scsi-hd,drive=disk-lvm-4,bus=scsi.0 chpst program is only used to run the guest under unprivileged user in a group which owns /dev/kvm grub.img is a 8MB disk image with GPT and single biosgrub partition. It is only used as a means to make guest's CPU spin on something, any other way should work as well. Observe CPU load with htop set to show detailed CPU time. CPU usage is no longer shown in cyan color (guest), it is shown in red (system) instead. Steal time accounting when running in a virtual machine seems to work correctly. (I removed PCI information included by reportbug since I don't think this is a hardware-related issue. If needed, I can provide it.) -- Package-specific info: ** Version: Linux version 5.10.0-6-amd64 (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.28-1 (2021-04-09) ** Command line: BOOT_IMAGE=/boot/vmlinuz-5.10.0-6-amd64 root=UUID=bc4aa9fd-9c63-445e-aeae-2147798879f4 ro amd_iommu=on intel_iommu=on net.ifnames=0 ** Not tainted ** Kernel log: [4.185348] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti [4.191508] PTP clock support registered [4.194579] ccp :42:00.1: SEV API:0.24 build:3 [4.264204] checking generic (b600 30) vs hw (b600 100) [4.264207] fb0: switching to astdrmfb from EFI VGA [4.268024] Console: switching to colour dummy device 80x25 [4.268247] ast :c4:00.0: [drm] P2A bridge disabled, using default configuration [4.268250] ast :c4:00.0: [drm] AST 2500 detected [4.268257] ast :c4:00.0: [drm] Analog VGA only [4.268259] ast :c4:00.0: [drm] dram MCLK=800 Mhz type=1 bus_width=16 [4.268804] [TTM] Zone kernel: Available graphics memory: 131929092 KiB [4.268807] [TTM] Zone dma32: Available graphics memory: 2097152 KiB [4.268808] [TTM] Initializing pool allocator [4.268812] [TTM] Initializing DMA pool allocator [4.269010] [drm] Initialized ast 0.1.0 20120228 for :c4:00.0 on minor 0 [4.273003] fbcon: astdrmfb (fb0) is primary device [4.284407] Console: switching to colour frame buffer device 128x48 [4.286804] ast :c4:00.0: [drm] fb0: astdrmfb frame buffer device [4.295928] tg3 :c6:00.0 eth0: Tigon3 [partno(BCM95720) rev 572] (PCI Express) MAC address ac:1f:6b:e5:e1:7e [4.296009] tg3 :c6:00.0 eth0: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) [4.296060] tg3 :c6:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] [4.296102] tg3 :c6:00.0 eth0: dma_rwctrl[0001] dma_mask[64-bit] [4.312469] tg3 :c6:00.1 eth1: Tigon3 [partno(BCM95720) rev 572] (PCI Express) MAC address ac:1f:6b:e5:e1:7f [4.312529] tg3 :c6:00.1 eth1: attached PHY is 5720C (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1]) [4.312582] tg3 :c6:00.1 eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] TSOcap[1] [4.312625] tg3 :c6:00.1 eth1: dma_rwctrl[0001] dma_mask[64-bit] [4.320397] input: PC Speaker as /devices/platform/pcspkr/input/input3 [4.329707] RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms ovfl timer [4.329951] RAPL PMU: hw unit of domain package 2^-16 Joules [4.336927] pstore: ignoring unexpected backend 'efi' [4.339850] cryptd: max_cpu_qlen set to 1000 [4.350152] AVX2 version of gcm_enc/dec engaged. [4.350175] AES CTR mode by8 optimization enabled [4.543242] kvm: Nested Virtualization enabled [4.543417] SVM: kvm: Nested Paging enabled [4.543430] SVM: Virtual VMLOAD VMSAVE supported [4.543444] SVM: Virtual GIF supported [4.548630] MCE: In-kernel MCE decoding enabled. [4.551186] EDAC amd64: F17h_M30h detected (node 0). [4.560369] EDAC amd64: Node 0: DRAM ECC enabled. [4.561135] EDAC amd64: MCT channel count: 8 [4.562760] EDAC MC0: Giving out device to module amd64_edac controller F17h_M30h: DEV :00:18.3 (INTERRUPT) [4.566733] EDAC MC: UMC0 chip selects: [4.566735] EDAC amd64: MC: 0: 16384MB 1: 16384MB [4.567578] EDAC amd64: MC: 2: 0MB 3: 0MB [4.569941] EDAC MC: UMC1 chip selects: [4.569942] EDAC amd64: MC: 0: 16384MB 1: 16384MB [4.570596] EDAC amd64: MC: 2: 0MB 3: 0MB [
Bug#927184: linux-image-4.19.0-4-amd64: Linux 4.19 reports wrong numbers for disks in /proc/diskstats
Package: linux-source-4.19 Version: 4.19.160-2 Followup-For: Bug #927184 We got hit by this bug after updating to most recent kernel version. In our case it affected all disk drives, regardless of their type (rotating or SSD.) After some research, we found out that the issue was triggered by change of default I/O scheduler done by us before the update (and taking effect after restart.) See the following console output: root@server:~# cat /sys/block/sde/queue/scheduler [mq-deadline] none root@server:~# for a in $( seq 1 5 ) ; do sleep 1 ; cat /sys/block/sde/stat ; done 11452700 133667 706138701 5139372 168800292 66117118 3870603434 780798520 1156352620 1170874630 18194850 349746784 1614457 11452700 133667 706138701 5139372 168800309 66117137 3870603746 780798620 1156352630 1170874640 18194850 349746784 1614457 11452700 133667 706138701 5139372 168800417 66117189 3870604914 780799110 1156352640 1170874650 18194850 349746784 1614457 11452700 133667 706138701 5139372 168800431 66117205 3870605154 780800140 1156352740 1170874750 18194850 349746784 1614457 11452700 133667 706138701 5139372 168800491 66117250 3870606090 780800370 1156352750 1170874760 18194860 349746792 1614457 root@server:~# echo "none"> /sys/block/sde/queue/scheduler root@server:~# for a in $( seq 1 5 ) ; do sleep 1 ; cat /sys/block/sde/stat ; done 11452709 133667 706138965 5139376 168803680 66118376 3870643746 780816460 1156354860 1170878030 18194880 349746808 1614459 11452710 133667 706138997 5139377 168804363 66118550 3870650634 780819620 1156355800 1170879210 18194890 349746816 1614459 11452710 133667 706138997 5139377 168804439 66118594 3870651642 780819930 1156356740 1170880150 18194890 349746816 1614459 11452710 133667 706138997 5139377 168804498 66118653 3870652762 780820220 1156357680 1170881090 18194890 349746816 1614459 11452710 133667 706138997 5139377 168804569 66118700 3870653834 780820530 1156358630 1170882040 18194890 349746816 1614459 root@server:~# echo "mq-deadline"> /sys/block/sde/queue/scheduler root@server:~# for a in $( seq 1 5 ) ; do sleep 1 ; cat /sys/block/sde/stat ; done 11452710 133667 706138997 5139377 168804885 66118930 3870658594 780822080 1156361540 1170884950 18194910 349779592 1614461 11452710 133667 706138997 5139377 168804942 66118957 3870659346 780822360 1156361570 1170884980 18194910 349779592 1614461 11452711 133667 706139005 5139377 168805194 66119062 3870673810 780823460 1156361630 1170885050 18194910 349779592 1614461 11452711 133667 706139005 5139377 168805240 66119088 3870674394 780823680 1156361630 1170885050 18194910 349779592 1614461 11452711 133667 706139005 5139377 168805464 66119186 3870688410 780824570 1156361670 1170885130 18194910 349779592 1614461 As long as mq-deadline scheduler is active, all works well, value in 10th column is increasing by realistic steps. After switching to none scheduler, the steps increase to almost a second whenever there is at least some activity on the drive. That in turn shows as almost 100% disk utilization in tools that use these values. Note that the value in 10th column is supposed to be increasing when value in 9th column is non-zero (according to https://www.kernel.org/doc/Documentation/iostats.txt ), yet I saw no occurence of non-zero number in that column in my testing, which does not correspond to device under 100% load. Using mq-deadline in virtual machines and for SSDs is most likely not optimal, but as a workaround, switching to mq-deadline works.
Bug#926202: closing 926202
Hello, sorry for the delayed reply, apparently the only e-mail that was sent to this address was the one about the bug being closed. Tried the same thing as when I initially reported the bug - syncing multiple RAID1 arrays while doing pvmove between them. No errors were logged, everything seems fine. This indeed seems fixed, thanks.
Bug#949248: nftables: nft parsing from stdin fails but works from file
Package: nftables Version: 0.9.0-2 Severity: normal I want to parse rules from a script but parsing them from a pipe files while parsing from file works nft -f nft.txt works cat nft.txt | nft -f - fails with a handful of syntax errors I also noticed a difference when doing full debug output Reading Cfrom file shows the filename, the line number and the postion as well as the actual line and the used part of line Reading from stdin just shows /dev/stdin, the line number and the position. So there seams to be different handling oft reading the input I encountered this too some time ago - according to strace, nft is reading rules in 8kB long blocks (so everything works fine until your rules grow) but after the block is read, nft attempts to seek few bytes back in the file. I guess it wants to do the next read from some kind of boundary. Anyway, seeking in stream obviously fails with ESPIPE - Illegal seek (I guess nft doesn't check return value here), another 8kB block is read but not from the file position nft wanted, resulting in syntax error. Nft man page says that reading from stdin is supported, but it also says that "nft export json" is a thing, so I just written this off as yet another error in the docs and worked around it by dumping my rules into a temporary file a reading them via -f . You may want to do the same thing.
Bug#944922: postfix: Init script in 3.4.7-2 does not start all instances
On 11. 02. 20 19:33, Scott Kitterman wrote:
On Tuesday, February 11, 2020 12:35:16 PM EST jaros...@thinline.cz
wrote:
On Sun, 12 Jan 2020 21:18:15 -0500 Scott Kitterman
wrote:
On Sun, 17 Nov 2019 12:04:46 -0600 Andy Dorman
wrote:
Package: postfix
Version: 3.4.7-2
Severity: normal
Dear Maintainer,
We have several servers that run three instances of postfix on our
own
hardware (not in a virtual machine environment).
The enabled_instances() command from line 32 of the
/etc/init.d/postfix
init
script shows the three instances:
Do you have multiple postfix master processes running? If so, where
are they
located?
Can you tell me the value of queue_directory for each instance?
Scott K
I've set up a docker image where I can use sysv init with multiple
instances
and they all start/stop fine. They were set up per the Postfix
MULTI_INSTANCE_README. I am unable to replicate your problem.
If you have multiple master processes running (not the standard
configuration),
then I can see how the new version might fail, but I can't make
progress on
this bug without input from you.
Scott K
Hello,
we got hit by this too during 10.2 to 10.3 update. Hotfixed it by
replacing running() function from the previous version of the init
script. (More on that below.)
Could you please clarify how having multiple master processes running
is
not the standard configuration? Our multiple instance setup was
created
according to Postfix MULTI_INSTANCE_README using these:
postmulti -e init
postmulti -e create -I postfix-fwd
and there has always been one master process per instance (same
binary,
but multiple processes spawning off it.) Even with systemd as init
system, there is one master process per instance (just tested on
Postfix
3.4.8-0+10debu1 on Debian 10.3)
About the running() function in the current 3.4.8 init script - in my
opinion its current form makes no sense. It's called with instance
name
as parameter by the for cycle in start) and stop) cases for each
instance in the system. However, this line:
daemon_directory=$($POSTCONF -hx daemon_directory 2>/dev/null || echo
/usr/lib/postfix/sbin)
is always returning the same directory: /usr/lib/postfix/sbin ,
regardless of the parameter passed to the function. Subsequent call to
/usr/lib/postfix/sbin/master -t then yields result regardless of the
parameter as well: it always returns the state of the main Postfix
instance, not the instance being checked by the caller.
Was there a reason to change this function? Previous version from
3.4.7
did the right thing here. Seemingly it even went beyong simple "pid
file
exists" check that "master -t" does, and checked if the PID inside the
file exists and is Postfix's master process.
Also, considering this now affects stable and causes regression on
update, increasing severity might be warranted.
There are environments where the old approach didn't work. I had
intended to
work on this sooner, but ran out of time. Changing priority won't give
me
more time to work on Postfix in Debian. This is the next thing I plan
to do.
The current version replicates the upstream approach, but obviously
something
else is different. My intent is to got back to the previous version of
the
function by default and only use the new one if /proc isn't accessible
(which
is the original problem I was trying to solve).
Sorry for the inconvenience.
Scott K
Hello,
thanks for putting your time into this.
If it helps, I made a quick and dirty fix to the new approach
running() {
INSTANCE="$1"
if [ "X$INSTANCE" = X ]; then
POSTMULTI=""
else
POSTMULTI="postmulti -i $INSTANCE -x "
fi
POSTCONF="${POSTMULTI} postconf"
daemon_directory=$($POSTCONF -hx daemon_directory 2>/dev/null ||
echo /usr/lib/postfix/sbin)
if ! ${POSTMULTI} $daemon_directory/master -t 2>/dev/null ; then
echo y
fi
}
This way postmulti calls master (or any program) with some environment
variables set, namely [1]:
MAIL_LOGTAG=postfix
MAIL_CONFIG=/etc/postfix-fwd
daemon_directory=/usr/lib/postfix/sbin
command_directory=/usr/sbin
config_directory=/etc/postfix-fwd
queue_directory=/var/spool/postfix-fwd
data_directory=/var/lib/postfix-fwd
multi_instance_name=postfix-fwd
multi_instance_group=
multi_instance_enable=yes
Apparently master process uses these and does the right thing, ie. looks
for the pidfile in correct directory - see strace:
[pid 8180] chdir("/var/spool/postfix-fwd") = 0
[pid 8180] access("pid/master.pid", F_OK) = 0
I admit I have no idea whatsoever if this approach is correct,
documented or supported. Just occured to me it might work and it did.
[1] postmulti -i postfix-fwd -x cat /proc/self/environ | tr "\0" "\n"
Bug#944922: postfix: Init script in 3.4.7-2 does not start all instances
On Sun, 12 Jan 2020 21:18:15 -0500 Scott Kitterman wrote: On Sun, 17 Nov 2019 12:04:46 -0600 Andy Dorman wrote: > Package: postfix > Version: 3.4.7-2 > Severity: normal > > Dear Maintainer, > > We have several servers that run three instances of postfix on our own hardware (not in a virtual machine environment). > > The enabled_instances() command from line 32 of the /etc/init.d/postfix init script shows the three instances: Do you have multiple postfix master processes running? If so, where are they located? Can you tell me the value of queue_directory for each instance? Scott K I've set up a docker image where I can use sysv init with multiple instances and they all start/stop fine. They were set up per the Postfix MULTI_INSTANCE_README. I am unable to replicate your problem. If you have multiple master processes running (not the standard configuration), then I can see how the new version might fail, but I can't make progress on this bug without input from you. Scott K Hello, we got hit by this too during 10.2 to 10.3 update. Hotfixed it by replacing running() function from the previous version of the init script. (More on that below.) Could you please clarify how having multiple master processes running is not the standard configuration? Our multiple instance setup was created according to Postfix MULTI_INSTANCE_README using these: postmulti -e init postmulti -e create -I postfix-fwd and there has always been one master process per instance (same binary, but multiple processes spawning off it.) Even with systemd as init system, there is one master process per instance (just tested on Postfix 3.4.8-0+10debu1 on Debian 10.3) About the running() function in the current 3.4.8 init script - in my opinion its current form makes no sense. It's called with instance name as parameter by the for cycle in start) and stop) cases for each instance in the system. However, this line: daemon_directory=$($POSTCONF -hx daemon_directory 2>/dev/null || echo /usr/lib/postfix/sbin) is always returning the same directory: /usr/lib/postfix/sbin , regardless of the parameter passed to the function. Subsequent call to /usr/lib/postfix/sbin/master -t then yields result regardless of the parameter as well: it always returns the state of the main Postfix instance, not the instance being checked by the caller. Was there a reason to change this function? Previous version from 3.4.7 did the right thing here. Seemingly it even went beyong simple "pid file exists" check that "master -t" does, and checked if the PID inside the file exists and is Postfix's master process. Also, considering this now affects stable and causes regression on update, increasing severity might be warranted.
Bug#926411: Export to json/xml doesn't work
Package: nftables
Version: 0.9.0-2
Severity: normal
Hello,
according to the nft man page, it is possible to export current ruleset
to JSON or XML format using this command:
nft export [ruleset] format
where format is a mandatory parameter and "may be either xml or json".
Using
the export command without format indeed raises an error:
# nft export
Error: syntax error, unexpected newline, expecting ruleset or xml or
json or vm
However, adding the format does not work either:
# nft export json
Error: this output type is not supported
This used to work in nftables 0.7-1 in Stretch (example with no rules
present)
# nft export json
{"nftables":[]}
Export to JSON allows automated processing of the ruleset and it would
be nice
to have it functional. Or - if the current state is not a regression but
an intentional change - it should be reflected in the man page.
Thanks
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages nftables depends on:
ii dpkg 1.19.5
ii libc6 2.28-8
ii libgmp10 2:6.1.2+dfsg-4
ii libjansson4 2.12-1
ii libnftables0 0.9.0-2
ii libreadline7 7.0-5
nftables recommends no packages.
nftables suggests no packages.
-- no debconf information
Bug#926202: mpt3sas driver stuck in endless resetting loop under load
Package: linux-image-4.19.0-0.bpo.2-amd64 Version: 4.19.16-1~bpo9+1 When testing 4.19 from backports, we ran into an issue which manifests under heavy I/O load. The driver gets stuck in endless resetting loop, affecting I/O performance badly. Affected server uses Supermicro H11DSi-NT motherboard and LSI 3008 HBA (Supermicro part number is AOC-S3008L-L8I). Six software (Linux MD) RAID1 arrays are formed from 12 drives (6 rotating, 6 SSDs). The issue can be triggered reliably by forcing the arrays to resync (with sync_speed_max set to 60 for all of them) and running pvmove between two of the SSD arrays at the same time. After few seconds the server becomes unresponsive, array resync speed drops to near zero, same for pvmove progress. Accesing files which are not present in memory (or saving files) takes several seconds. For testing purposes, we tried to move all the hard drives into another server that has the same LSI hardware, but the issue persisted. Neither of those servers is in production use yet, so we should be able to test potential solutions and patches easily. This is logged in dmesg (triple dot indicates same message repeating for different drives): [ 242.680063] mpt3sas_cm0: fault_state(0x5862)! [ 242.680114] mpt3sas_cm0: sending diag reset !! [ 243.713254] mpt3sas_cm0: diag reset: SUCCESS [ 243.742277] mpt3sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k [ 243.897265] mpt3sas_cm0: _base_display_fwpkg_version: complete [ 243.897639] mpt3sas_cm0: LSISAS3008: FWVersion(16.00.01.00), ChipRevision(0x02), BiosVersion(08.37.00.00) [ 243.897705] mpt3sas_cm0: Protocol=( [ 243.897706] Initiator [ 243.897732] ,Target [ 243.897752] ), [ 243.897770] Capabilities=( [ 243.897785] TLR [ 243.897806] ,EEDP [ 243.897821] ,Snapshot Buffer [ 243.897837] ,Diag Trace Buffer [ 243.897859] ,Task Set Full [ 243.897883] ,NCQ [ 243.897904] ) [ 243.897988] mpt3sas_cm0: sending port enable !! [ 251.003196] mpt3sas_cm0: port enable: SUCCESS [ 251.003376] mpt3sas_cm0: search for end-devices: start [ 251.003835] scsi target0:0:0: handle(0x000a), sas_addr(0x50030480180580c0) [ 251.003886] scsi target0:0:0: enclosure logical id(0x50030480180580ff), slot(0) [ 251.003980] scsi target0:0:1: handle(0x000b), sas_addr(0x50030480180580c1) [ 251.004029] scsi target0:0:1: enclosure logical id(0x50030480180580ff), slot(1) ... [ 251.021639] scsi target0:0:12: handle(0x0016), sas_addr(0x50030480180580fd) [ 251.022166] scsi target0:0:12: enclosure logical id(0x50030480180580ff), slot(12) [ 251.022740] mpt3sas_cm0: search for end-devices: complete [ 251.023281] mpt3sas_cm0: search for end-devices: start [ 251.023817] mpt3sas_cm0: search for PCIe end-devices: complete [ 251.024365] mpt3sas_cm0: search for expanders: start [ 251.024934] expander present: handle(0x0009), sas_addr(0x50030480180580ff) [ 251.025502] mpt3sas_cm0: search for expanders: complete [ 251.026038] mpt3sas_cm0: _base_fault_reset_work: hard reset: success [ 251.026086] mpt3sas_cm0: removing unresponding devices: start [ 251.028140] mpt3sas_cm0: removing unresponding devices: end-devices [ 251.029484] mpt3sas_cm0: Removing unresponding devices: pcie end-devices [ 251.030795] mpt3sas_cm0: removing unresponding devices: expanders [ 251.032106] mpt3sas_cm0: removing unresponding devices: complete [ 251.033412] mpt3sas_cm0: scan devices: start [ 251.035183] mpt3sas_cm0: scan devices: expanders start [ 251.038769] mpt3sas_cm0: break from expander scan: ioc_status(0x0022), loginfo(0x310f0400) [ 251.040140] mpt3sas_cm0: scan devices: expanders complete [ 251.041496] mpt3sas_cm0: scan devices: end devices start [ 251.043860] mpt3sas_cm0: break from end device scan: ioc_status(0x0022), loginfo(0x310f0400) [ 251.044991] mpt3sas_cm0: scan devices: end devices complete [ 251.046109] mpt3sas_cm0: scan devices: pcie end devices start [ 251.047237] mpt3sas_cm0: log_info(0x3003011d): originator(IOP), code(0x03), sub_code(0x011d) [ 251.048402] mpt3sas_cm0: log_info(0x3003011d): originator(IOP), code(0x03), sub_code(0x011d) [ 251.049505] mpt3sas_cm0: break from pcie end device scan: ioc_status(0x0021), loginfo(0x3003011d) [ 251.050319] mpt3sas_cm0: pcie devices: pcie end devices complete [ 251.050966] mpt3sas_cm0: scan devices: complete [ 251.503219] sd 0:0:0:0: Power-on or device reset occurred [ 251.503261] sd 0:0:2:0: Power-on or device reset occurred ... [ 252.007740] sd 0:0:8:0: Power-on or device reset occurred One second later the kernel logs [ 253.080085] mpt3sas_cm0: fault_state(0x5862)! and the whole process repeats itself. It keeps repeating until the server is shut down. lspci info for the HBA is: 02:00.0 Serial Attached SCSI controller [0107]: LSI Logic / Symbios Logic SAS3008 PCI-Express Fusion-MPT SAS-3 [1000:0097] (rev 02) This issue appears to be similar to one I found in Ubuntu bug tracker -
Bug#925509: netbeans: Netbeans not usable with java in Buster
Dne středa 27. března 2019 12:42:54 CEST, Markus Koschany napsal(a): > Control: forcemerge 925509 925510 > Control: severity -1 serious > > Am 25.03.19 um 23:26 schrieb Wouter Wijsman: > [...] > > > A java.lang.NoSuchMethodError exception has occurred. > > Please report this at > > https://issues.apache.org/jira/projects/NETBEANS/issues, > > including a copy of your messages.log file as an attachment. > > The messages.log file is located in your > > /home/wouter/.netbeans/10.0/var/log folder. > > > > The full log can be found here: https://pastebin.com/0wgJNt15 > > > > I hope that helps. I can provide more information if needed. > > Hello and thanks for reporting! > > java.lang.NoSuchMethodError: > com.sun.tools.javadoc.main.JavadocClassFinder: method > (Lcom/sun/tools/javac/util/Context;)V not found > > This look like an incompatibility with Java 11. > > Jaroslav and Jan, might this be related to nb-javac again? Here is the > full log. > > https://pastebin.com/0wgJNt15 > > and the link to the full bug report. > > https://bugs.debian.org/925509 Hello Markus, it would be better to have a whole NetBeans log file instead of just the stack trace. Then we could see classpath, list of enabled modules and may be deduce more. Best regards. -jt
Bug#813164: coreutils: ls suddenly quotes output
Hi, please revert this ugly change, it's confusing and against GNU coding standards [1]: > Likewise, please don’t make the behavior of a command-line program depend > on the type of output device it gets as standard output or standard input. > Device independence is an important principle of the system’s design; > do not compromise it merely to save someone from typing an option now and > then. > (Variation in error message syntax when using a terminal is ok, > because that is a side issue that people do not depend on.) and: > Compatibility requires certain programs to depend on the type of output > device. > It would be disastrous if ls or sh did not do so in the way all users expect. I think most of the users including me do not expect 'ls' to behave such strange way thanks & regards Jaroslav [1] http://www.gnu.org/prep/standards/standards.html#User-Interfaces
Bug#813164: coreutils: ls suddenly quotes output
- Original Message - > On 12/02/16 01:47, Jaroslav Skarvada wrote: > > Hi, > > > > please revert this ugly change, it's confusing and against GNU coding > > standards [1]: > > > >> Likewise, please don’t make the behavior of a command-line program depend > >> on the type of output device it gets as standard output or standard input > > ls already changed output depending on if output is a tty > We really don't want to adhere to that guideline for ls. > I know that's why there is 'dir' command, but please do not make the situation worse by diverging the outputs even more in a such confusing way (in default configuration).
Bug#814477: python-pkg-resources: Package from backports break functioning of python apps
Package: python-pkg-resources Version: 18.8-1~bpo8+1 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? Installing package from backports branch (and newer, i.e. from sid) break many python software unusable. * What exactly did you do (or not do) that was effective (or ineffective)? Try to run apps, like bpython and many others. Try this for example: Example in python: >>> from pkg_resources import load_entry_point * What was the outcome of this action? Traceback (most recent call last): File "", line 1, in File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3138, in @_call_aside File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3124, in _call_aside f(*args, **kwargs) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3151, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 652, in _build_master ws = cls() File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 645, in __init__ self.add_entry(entry) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 701, in add_entry for dist in find_distributions(entry, True): File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2139, in find_on_path path_item, entry, metadata, precedence=DEVELOP_DIST File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2521, in from_location py_version=py_version, platform=platform, **kw File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2835, in _reload_version md_version = _version_from_file(self._get_metadata(self.PKG_INFO)) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2486, in _version_from_file line = next(iter(version_lines), '') File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2654, in _get_metadata for line in self.get_metadata_lines(name): File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2030, in get_metadata_lines return yield_lines(self.get_metadata(name)) File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2025, in get_metadata metadata = f.read() File "/usr/lib/python2.7/codecs.py", line 296, in decode (result, consumed) = self._buffer_decode(data, self.errors, final) UnicodeDecodeError: 'utf8' codec can't decode byte 0xb6 in position 147: invalid start byte * What outcome did you expect instead? Importing from pkg_resources module OK, like in module from stable branch work. -- System Information: Debian Release: 8.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.3.0-0.bpo.1-amd64 (SMP w/4 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python-pkg-resources depends on: pn python:any python-pkg-resources recommends no packages. Versions of packages python-pkg-resources suggests: ii python-setuptools 18.8-1~bpo8+1 -- no debconf information
Bug#759481: Patches for sorting radiobuttons and deprecating SHA-1
Hi,
attached patches are also available at
https://github.com/benkovsk/tinyca2_debian/tree/sort_radiobuttons
0001-Alphasort-radiobuttons-to-get-somewhat-sensible-orde.patch
Alphasort radiobuttons to get somewhat sensible order (e.g. when
creating a new request), so that radiobutton for MD4 is not wedged in
between SHA-384 and SHA-512
0002-Mark-SHA-1-as-insecure.patch
Since the shappenning paper, SHA-1's days are probably numbered,
so mark it as insecure already
The patches against Christian Simon's repository, i.e. with SHA-2
patches already included.
Cheers,
Jaroslav Benkovsky
>From f9deaab23b5c30cd755e021191e5888d0eb643b3 Mon Sep 17 00:00:00 2001
From: Fred-Builder <jaroslav.benkov...@nic.cz>
Date: Tue, 13 Oct 2015 12:01:35 +0200
Subject: [PATCH 1/2] Alphasort radiobuttons to get somewhat sensible order
---
lib/GUI.pm |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/GUI.pm b/lib/GUI.pm
index 0805b16..0c18ed8 100644
--- a/lib/GUI.pm
+++ b/lib/GUI.pm
@@ -3096,7 +3096,7 @@ sub _fill_radiobox {
my($previous_key, $value);
$previous_key = undef;
- for $value (keys %values) {
+ for $value (sort keys %values) {
my $display_name = $values{$value};
my $key = Gtk2::RadioButton->new($previous_key, $display_name);
$key->signal_connect('toggled' =>
--
1.7.9.5
>From 9e79ff9c4a37861e46f9fba9d5e37ed42cdd4167 Mon Sep 17 00:00:00 2001
From: Fred-Builder <jaroslav.benkov...@nic.cz>
Date: Tue, 13 Oct 2015 12:04:58 +0200
Subject: [PATCH 2/2] Mark SHA-1 as insecure
* since the shappenning paper, its days are
probably numbered
---
lib/GUI.pm |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/GUI.pm b/lib/GUI.pm
index 0c18ed8..0a8c3a9 100644
--- a/lib/GUI.pm
+++ b/lib/GUI.pm
@@ -36,7 +36,7 @@ my %md_algorithms = (
'md4' => 'ins.MD4',
'ripemd160' => 'RIPEMD-160',
# 'sha' => 'SHA',
- 'sha1' => 'SHA-1',
+ 'sha1' => 'ins.SHA-1',
'sha256' => 'SHA-256',
'sha384' => 'SHA-384',
'sha512' => 'SHA-512',
--
1.7.9.5
Bug#779078: apache2-bin: event mpm: child segfault in notify_suspend causes parent to exit during log rotation
We got hit by this bug too and reported it to upstream. See https://bz.apache.org/bugzilla/show_bug.cgi?id=57268 , applying the patch suggested in there to Debian source solved the issue for us. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#776248: fuseext2: CPU at 100% when mounting ext4 fs with block size 4K
Package: fuseext2 Version: 0.4-1.1 Severity: normal Dear Maintainer, * What led up to the situation? When using fuseext2 for mounting filesystem with block size 4K, 1 CPU core is at 100% and directory with mount point is busy (when file image is mounted, then directory with this file is busy too). * What exactly did you do (or not do) that was effective (or ineffective)? i.e.: $ dd if=/dev/zero of=ext4-bs64k.img bs=1M seek=1M count=0 $ sudo /sbin/mkfs.ext4 -L TestExtFS -b 65536 ext4-bs64k.img $ fuseext2 ext4-bs64k.img /mount/somewhere/you/want * What was the outcome of this action? Filesystem is mounted without errors, but when any operation (i.e. ls -l) on mount point cause 100% of 1 CPU core and there is no expected output from operation. * What outcome did you expect instead? Working with mounted filesystem as usually (ls, cp, mv, mkdir, rm, rmdir, etc.) Sincerely Jarda -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing-proposed-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages fuseext2 depends on: ii e2fslibs 1.42.12-1 ii fuse 2.9.3-15+b1 ii libc6 2.19-13 ii libfuse2 2.9.3-15+b1 fuseext2 recommends no packages. fuseext2 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#767355: Patch for System.EntryPointNotFoundException: CreateCaret
I am not exactly sure what is causing this exception but the stack trace contains only System.* namespaces so the problem will most likely be in mono implementation of winforms. My testing shows that this exception is related only to hexbox package (libhexbox package is unaffected) and the application functionality seems to be unaffected also - it is just an exception printed into the console when the application is closed. I think it can be ignored. BTW I have examined debian/control file of the package and it seems the descriptions for hexbox and libhexbox packages are swapped. Regards, Jaroslav On Tue, Nov 18, 2014 at 12:36 PM, Mathieu Malaterre ma...@debian.org wrote: Control: tags -1 pending On Mon, Nov 17, 2014 at 3:14 PM, Mathieu Malaterre ma...@debian.org wrote: Control: tags -1 patch On Mon, Nov 17, 2014 at 3:08 PM, Jaroslav Imrich ja...@jariq.sk wrote: Hello Mathew, I have developed a patch [1] for HexBox control 1.6.0 that disables usage of carets when required unmanaged functions are not available in the runtime platform.With this patch caret is not displayed on Linux with Mono runtime but other than that HexBox control is still perfectly usable. Feel free to incorporate these changes into your package or contact me if you need any help with that. [1] https://github.com/jariq/Be.HexEditor/commit/c05c5df1358bf5427dd2fcec0e392a132cd69422 Wow ! Thanks much, will try asap. Jaroslav, Do you know why I get the following (simply start close hexbox, you do not need to even open a file): $ hexbox Unhandled Exception: System.ArgumentException: A null reference or invalid value was found [GDI+ status: InvalidParameter] at System.Drawing.GDIPlus.CheckStatus (Status status) [0x0] in filename unknown:0 at System.Drawing.Graphics.GdipMeasureString (IntPtr graphics, System.String text, System.Drawing.Font font, System.Drawing.RectangleF layoutRect, IntPtr stringFormat) [0x0] in filename unknown:0 at System.Drawing.Graphics.MeasureString (System.String text, System.Drawing.Font font, Int32 width, System.Drawing.StringFormat format) [0x0] in filename unknown:0 at (wrapper remoting-invoke-with-check) System.Drawing.Graphics:MeasureString (string,System.Drawing.Font,int,System.Drawing.StringFormat) at System.Windows.Forms.TextRenderer.MeasureTextInternal (IDeviceContext dc, System.String text, System.Drawing.Font font, Size proposedSize, TextFormatFlags flags, Boolean useMeasureString) [0x0] in filename unknown:0 at System.Windows.Forms.TextRenderer.MeasureText (System.String text, System.Drawing.Font font, Size proposedSize, TextFormatFlags flags) [0x0] in filename unknown:0 at System.Windows.Forms.ToolStripItem.OnParentChanged (System.Windows.Forms.ToolStrip oldParent, System.Windows.Forms.ToolStrip newParent) [0x0] in filename unknown:0 at System.Windows.Forms.ToolStripItem.set_Parent (System.Windows.Forms.ToolStrip value) [0x0] in filename unknown:0 at (wrapper remoting-invoke-with-check) System.Windows.Forms.ToolStripItem:set_Parent (System.Windows.Forms.ToolStrip) at System.Windows.Forms.ToolStripItemCollection.Remove (System.Windows.Forms.ToolStripItem value) [0x0] in filename unknown:0 at System.Windows.Forms.ToolStripItem.Dispose (Boolean disposing) [0x0] in filename unknown:0 at System.Windows.Forms.ToolStripDropDownItem.Dispose (Boolean disposing) [0x0] in filename unknown:0 at System.Windows.Forms.ToolStripMenuItem.Dispose (Boolean disposing) [0x0] in filename unknown:0 at System.ComponentModel.Component.Finalize () [0x0] in filename unknown:0
Bug#767355: Patch for System.EntryPointNotFoundException: CreateCaret
Hello Mathew, I have developed a patch [1] for HexBox control 1.6.0 that disables usage of carets when required unmanaged functions are not available in the runtime platform.With this patch caret is not displayed on Linux with Mono runtime but other than that HexBox control is still perfectly usable. Feel free to incorporate these changes into your package or contact me if you need any help with that. [1] https://github.com/jariq/Be.HexEditor/commit/c05c5df1358bf5427dd2fcec0e392a132cd69422 Regards, Jaroslav
Bug#757887: systemd: kdm don't start
On 12.8.2014 10:31, Moritz Mühlenhoff wrote: On Tue, Aug 12, 2014 at 01:08:39AM +0200, Michael Biebl wrote: Am 12.08.2014 00:31, schrieb Jaroslav Mikulík: Package: systemd Version: 208-6 Severity: normal Dear Maintainer, * What led up to the situation? After recent upgrade to systemd, kdm on my machine don't start (4 core CPU). Strange that on older machine (1 core CPU) is kdm started OK. * What exactly did you do (or not do) that was effective (or ineffective)? In kdm.log I found this error: klauncher(1841) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(1780)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: Not connected to D-Bus server When KDM is started on manualy after boot, then it started OK. Please remove the workaround from /etc/rc.local. Then boot adding the following to the kernel command line: systemd.log_level=debug After that, attach the journalctl -alb to this bug report. I had the same problem with kdm (or at least very similar, don't remember the exact error message). I made a native systemd unit file which fixes the problem for me. Jaroslav, if you want to try it, it's at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754314 (unfortunately w/o any feedback from KDE maintainers since 5 weeks) Cheers, Moritz I enjoyed too soon... With kdm.service file added, don't work teamviewer (teamviewerd is started), I can't start manualy mysql daemon, when I need it. First try to start of mysql end with error, second start of mysql OK - strange. I investigate more... Disabled kdm.service, moved kdm script to /etc/init.d/ back, enabled service kdm, disabled readahead service of systemd and REMOVED file /.readahead* succesfully solved my problem! Now I have working boot as I expected without workarrounds and with original kdm boot script... Jarda -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757887: systemd: kdm don't start
On 12.8.2014 10:31, Moritz Mühlenhoff wrote: On Tue, Aug 12, 2014 at 01:08:39AM +0200, Michael Biebl wrote: Am 12.08.2014 00:31, schrieb Jaroslav Mikulík: Package: systemd Version: 208-6 Severity: normal Dear Maintainer, * What led up to the situation? After recent upgrade to systemd, kdm on my machine don't start (4 core CPU). Strange that on older machine (1 core CPU) is kdm started OK. * What exactly did you do (or not do) that was effective (or ineffective)? In kdm.log I found this error: klauncher(1841) kdemain: No DBUS session-bus found. Check if you have started the DBUS server. kdeinit4: Communication error with launcher. Exiting! kdmgreet(1780)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: Not connected to D-Bus server When KDM is started on manualy after boot, then it started OK. Please remove the workaround from /etc/rc.local. Then boot adding the following to the kernel command line: systemd.log_level=debug After that, attach the journalctl -alb to this bug report. I had the same problem with kdm (or at least very similar, don't remember the exact error message). I made a native systemd unit file which fixes the problem for me. Jaroslav, if you want to try it, it's at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754314 (unfortunately w/o any feedback from KDE maintainers since 5 weeks) Cheers, Moritz I can't see systemd unit file in this link, but I created /lib/systemd/system/kdm.service file from diff file from this thread, which my modification. Content of this service file: --- cut --- [Unit] Description=KDM Display Manager Conflicts=getty@tty1.service After=systemd-user-sessions.service getty@tty1.service plymouth-quit.service [Service] ExecStart=/usr/bin/kdm -nodaemon Restart=always IgnoreSIGPIPE=no [Install] Alias=display-manager.service WantedBy=multi-user.target --- cut --- After moving out /etc/init.d/kdm file and run systemctl enable kdm.service my PC boot to kdm well. Thank you for your hint ;-). Jarda -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757887: systemd: kdm don't start
On 12.8.2014 01:13, Michael Biebl wrote: Am 12.08.2014 00:31, schrieb Jaroslav Mikulík: systemctl show kdm say: --- cut --- Before=x-display-manager.target shutdown.target bootlogs.service multi- user.target graphical.target After=openvpn.service local-fs.target remote-fs.target console-screen.service kbd.service acpid.service dbus.serv ice krb5-kdc.service systemd-journald.socket basic.target system.slice --- cut --- dbus.service is started after kdm? Maybe this is the problem? No, this line says that kdm.service is started after dbus.service. Also, the error message talks about a D-Bus session bus, not the the D-Bus system bus. Can you also attach the output of systemctl status kdm.service (as root) when the service failed to start during boot. See attachment... Jarda kdm.service - LSB: X display manager for KDE Loaded: loaded (/etc/init.d/kdm) Drop-In: /run/systemd/generator/kdm.service.d ââ50-kdm-$x-display-manager.conf Active: failed (Result: exit-code) since St 2014-08-13 02:03:06 CEST; 1min 37s ago Process: 1362 ExecStart=/etc/init.d/kdm start (code=exited, status=219/CGROUP) srp 13 02:03:06 fanda systemd[1]: Child 1362 belongs to kdm.service srp 13 02:03:06 fanda systemd[1]: kdm.service: control process exited, code=exited status=219 srp 13 02:03:06 fanda systemd[1]: kdm.service got final SIGCHLD for state start srp 13 02:03:06 fanda systemd[1]: kdm.service changed start - failed srp 13 02:03:06 fanda systemd[1]: Job kdm.service/start finished, result=failed srp 13 02:03:06 fanda systemd[1]: Failed to start LSB: X display manager for KDE. srp 13 02:03:06 fanda systemd[1]: Unit kdm.service entered failed state. srp 13 02:03:06 fanda systemd[1]: kdm.service: cgroup is empty
Bug#692654: pptpd: Connection drop - problem in IDLE_WAIT implementation (sending ECHO REQ in file pptpctrl.c)
Package: pptpd Version: all versions Severity: important Dear Maintainer, Pptpd server does not sent keep-alive echo messages - echo reuests (RFC2637). If pptp client also does not send this echo messages then we have problem. Some firewalls and NAT drops connection after while (TCP connection timeout). We use mobile phones with Android. The pptp client in android does not send this echo messages. Connection is dropped after 150 seconds by our sbserver. This problem was fixed in revision 1.22 with patch Mon Jun 15 03:01:09 2009 UTC (3 years, 4 months ago). http://poptop.cvs.sourceforge.net/viewvc/poptop/poptop/pptpctrl.c?view=log Please use a patched version of poptop. -- System Information: Debian Release: wheezy/sid APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Bug#689341: openoffice.org-calc silently drops data when importing large html table
On Mon, Oct 01, 2012 at 07:46:46PM +0200, Rene Engelhard wrote: On Mon, Oct 01, 2012 at 07:18:16PM +0200, Jaroslav Janacek wrote: When importing an html table containing more than 65533 non-empty cells as web page query type document into openoffice.org-cals, calc only imports the first 65533 cells plus following cells containing up to about 16368 bytes cells? You mean rows? If yes, that's a limitation of OOo in that version. It simply cannot handle more rows. This was fixed in OOo 3.3 rcsomething (thus in Debian in LO 3.3). Regards, Rene No, I really mean cells (e.g. 1024 rows with 64 columns). I have just tested it at another machine with Libre Office 3.3.4 (OOO330m19 Build 401) (not Debian) and it behaves exactly in the same way. I'll see if I can find a Debian testing machine with LO, test it and submit the bug against that version. With regards, Jaroslav -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689341: openoffice.org-calc silently drops data when importing large html table
Package: openoffice.org-calc Version: 1:3.2.1-11+squeeze7 Severity: normal When importing an html table containing more than 65533 non-empty cells as web page query type document into openoffice.org-cals, calc only imports the first 65533 cells plus following cells containing up to about 16368 bytes of data (not counting the html tags). The remaining data are silently ignored. No warning or error is displayed. -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: i386 (i686) Kernel: Linux 3.2.0-0.bpo.3-686-pae (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 openoffice.org-calc depends on: ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libstdc++64.4.5-8The GNU Standard C++ Library v3 ii libstlport4.6 4.6.2-7STLport C++ class library ii lp-solve 5.5.0.13-7 Solve (mixed integer) linear progr ii openoffice.or 1:3.2.1-11+squeeze7office productivity suite -- share ii openoffice.or 1:3.2.1-11+squeeze7office productivity suite -- arch- ii ure 1.6.1+OOo3.2.1-11+squeeze7 OpenOffice.org UNO runtime environ openoffice.org-calc recommends no packages. openoffice.org-calc suggests no packages. Versions of packages openoffice.org-core depends on: ii fontconfig2.8.0-2.1 generic font configuration library ii libc6 2.11.3-3 Embedded GNU C Library: Shared lib ii libcairo2 1.8.10-6 The Cairo 2D vector graphics libra ii libcurl3-gnut 7.21.0-2.1+squeeze2Multi-protocol file transfer libra ii libdb4.8 4.8.30-2 Berkeley v4.8 Database Libraries [ ii libexpat1 2.0.1-7+squeeze1 XML parsing C library - runtime li ii libfreetype6 2.4.2-2.1+squeeze4 FreeType 2 font engine, shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libglib2.0-0 2.24.2-1 The GLib library of C routines ii libgraphite3 1:2.3.1-0.2SILGraphite - a smart font rende ii libgstreamer- 0.10.30-1 GStreamer libraries from the base ii libgstreamer0 0.10.30-1 Core GStreamer libraries and eleme ii libgtk2.0-0 2.20.1-2 The GTK+ graphical user interface ii libhunspell-1 1.2.11-1 spell checker and morphological an ii libhyphen02.5-1 ALTLinux hyphenation library - sha ii libice6 2:1.0.6-2 X11 Inter-Client Exchange library ii libicu44 4.4.1-8International Components for Unico ii libjpeg62 6b1-1 The Independent JPEG Group's JPEG ii libmythes-1.2 2:1.2.1-1 simple thesaurus library ii libneon27-gnu 0.29.3-3 An HTTP and WebDAV client library ii libnspr4-0d 4.8.6-1NetScape Portable Runtime Library ii libnss3-1d3.12.8-1+squeeze5 Network Security Service libraries ii librdf0 1.0.10-3 Redland Resource Description Frame ii libsm62:1.1.1-1 X11 Session Management library ii libssl0.9.8 0.9.8o-4squeeze13 SSL shared libraries ii libstdc++64.4.5-8The GNU Standard C++ Library v3 ii libstlport4.6 4.6.2-7STLport C++ class library ii libx11-6 2:1.3.3-4 X11 client-side library ii libxaw7 2:1.0.7-1 X11 Athena Widget library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxinerama1 2:1.1-3X11 Xinerama extension library ii libxml2 2.7.8.dfsg-2+squeeze5 GNOME XML library ii libxrandr22:1.3.0-3 X11 RandR extension library ii libxrender1 1:0.9.6-1 X Rendering Extension client libra ii libxslt1.11.1.26-6 XSLT 1.0 processing library - runt ii libxt61:1.0.7-1 X11 toolkit intrinsics library ii openoffice.or 1:3.2.1-11+squeeze7office productivity suite -- arch- ii ttf-opensymbo 1:3.2.1-11+squeeze7OpenSymbol TrueType font ii ure 1.6.1+OOo3.2.1-11+squeeze7 OpenOffice.org UNO runtime environ ii zlib1g1:1.2.3.4.dfsg-3 compression library - runtime -- 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#631113: bin/otrs.DeleteCache.pl (and other commands) lie about options
Package: otrs2 Version: 3.0.8+dfsg1-1 Default crontab file (/etc/otrs/cron, $HOME/var/cron/cache.dist) calls bin/otrs.DeleteCache.pl --expired , which does not work: $ bin/otrs.DeleteCache.pl --expired ERROR: Invalid option --expired! Indeed cursory review of the said script shows that it should be called with -e expired if at all. Script's helpstring advertises --expired. There are more discrepancies between helpstrings and actually implemented options in other scripts as well. Cheers, Jarda Benkovsky -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#591318: [PATCH] alsa-lib: Fix typo in comment in surround71.conf
Applied to our GIT repo. - Jaroslav Kysela pe...@perex.cz Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569779: ITP: ipwatchd -- IP conflict detection tool
Package: wnpp Severity: wishlist IPwatchD is a simple daemon that analyses all incoming ARP packets in order to detect IP conflicts on Linux. It can be configured to listen on one or more interfaces (alias interfaces are also supported) in active or passive mode. In active mode IPwatchD protects your host before IP takeover by answering Gratuitous ARP requests received from conflicting system. In passive mode it just records information about conflict through standard syslog interface. WEB: http://ipwatchd.sourceforge.net/ License: GPL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5e8d025d1002140100j62e4e8dbj5b70027bef9b4...@mail.gmail.com
Bug#569780: ITP: ipwatchd-gnotify -- Gnome notification tool for IPwatchD
Package: wnpp Severity: wishlist IPwatchD-G-Notify is notification tool for Gnome environment used by IPwatchD daemon to display notification bubble when IP conflict occurs. WEB: http://ipwatchd.sourceforge.net/ License: GPL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5e8d025d1002140103k26c7e822k3f815ace856c1...@mail.gmail.com
Bug#550823: Updating load-path cache based on modification times probably a bad idea (was: Race condition between Octave 3.2.3 and unlink())
2009/10/20 Thomas Weber thomas.weber.m...@gmail.com: Hi, On Thu, Oct 15, 2009 at 02:09:30PM +, Sébastien Villemot wrote: Hi, I think I found the culprit for what I thought was a race condition in Octave. The problem has to do with the way Octave 3.2 updates its load-path: it only updates its cache of the current directory if the modification time of the directory changes (see load_path::dir_info::update() in src/load-path.cc). In case it's not clear: this is a real problem and not some artificially found issue. It makes software using Octave randomly fail at build time. Thomas I don't understand - what you mean by build time? Most software using Octave is not dynamically creating m-files, so is not affected. The problem is in load_path::update, which checks the directory's modification time to decide on whether to rescan it. The resolution is only in seconds, though. But some check is surely wanted because you want to avoid useless rescans. I don't have a better idea. One could even say this is a limitation of the system, which provides no way to tell whether the directory has changed during the last second. Maybe rehash() could ignore the stamp for some directories? But which ones? -- RNDr. Jaroslav Hajek computing expert GNU Octave developer Aeronautical Research and Test Institute (VZLU) Prague, Czech Republic url: www.highegg.matfyz.cz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#544607: [alsa-devel] [Pkg-alsa-devel] Bug#544607: /usr/share/alsa/init/default:52: missing closing brace for format
On Wed, 2 Sep 2009, Elimar Riesebieter wrote:
forward 544607 alsa-de...@alsa-project.org
-ENV{has_pmaster_vol}==true,CTL{values)=100%,GOTO=headphone0_end
+ENV{has_pmaster_vol}==true,CTL{values}=100%,GOTO=headphone0_end
The change was commited to the alsa-utils repository. Thanks.
Jaroslav Kysela
-
Jaroslav Kysela pe...@perex.cz
Linux Kernel Sound Maintainer
ALSA Project, Red Hat, Inc.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519814: mime-support: Bad mime-type detection in run-mailcap
Package: mime-support Version: 3.44-1 Severity: important Hello, a mime-type detection in run-mailcap is not working correctly. For example: $ run-mailcap --debug=1 /etc/protocols - parsing parameter /etc/protocols - file /etc/protocols does not conform to any known pattern Warning: unknown mime-type for /etc/protocols -- using application/octet-stream But file utility is working well: $ file /etc/protocols /etc/protocols: ASCII English text It seems to happen with text/* mime-types (not all of them, though). -- System Information: Debian Release: 5.0 APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash mime-support depends on no packages. Versions of packages mime-support recommends: ii file 4.26-1 Determines file type using magic mime-support 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#519126: qrupdate fails to build in Debian on some architectures
On Wed, Mar 11, 2009 at 12:21 AM, peter green plugw...@p10link.net wrote: The bug is about an optimisation flag that we shouldn't just get rid of. At some point soon, I'll read the gcc manpage and figure out what a proper flag for other architectures should be. http://gcc.gnu.org/onlinedocs/gcc-4.3.3/gcc/i386-and-x86_002d64-Options.html#i386-and-x86_002d64-Options has the following to say about -march=native /native/ This selects the CPU to tune for at compilation time by determining the processor type of the compiling machine. Using -mtune=native will produce code optimized for the local machine under the constraints of the selected instruction set. Using -march=native will enable all instruction subsets supported by the local machine (hence the result might not run on different machines). In other words this flag is totally inappropriate for a binary distribution like debian. I removed the march=native flag from Makeconf. I have also uploaded an updated source tarball containing this fix and all the fixes to makefiles configuration files contributed by Jordi (no actual source code changed). cheers -- RNDr. Jaroslav Hajek computing expert GNU Octave developer Aeronautical Research and Test Institute (VZLU) Prague, Czech Republic url: www.highegg.matfyz.cz -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#308619: As the novelty of
DickMountainousPaula http://www.Twalveen.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#186102: Guaranteed gains in length and thickness
If she's petite, then this solution to gain inches is probably not for you, as being too large can hurt her - http://ipsoneda.com/ 554626534 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#118337: New online vacancies in our company United States.
International company Dex. Union Inc is looking for top candidates for a number of opportunities: Sales representative, Finance representative. We are searching for individuals in United States who have the intellectual capacity and interested in good earnings. Get job in 3 hours after your answer, and start earning! No relocation, cell phone and email required. High Salary! If you're seeking a convenient job location, consistent hours and great opportunity for growth than this is the perfect position for you in USA! Company Details and How to apply? Please write: [EMAIL PROTECTED] Regards Adam Nelson Dex. Union Inc. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#438118: [alsa-devel] [Pkg-alsa-devel] Bug#438118: alsa-utils: aplay non-blocking mode isn't working
On Fri, 14 Dec 2007, Anders Boström wrote: TI == Takashi Iwai [EMAIL PROTECTED] writes: TI OK, thanks, I see the problem now. TI I don't remember whether it's a feature or a bug. The drain ioctl TI rejects the non-block mode. I can understand the idea here, that in non-blocking mode, no call should block, ever. But on the other hand, if you call the drain ioctl, you probably expect it to work, even in non-blocking mode. Why would you otherwise call it? TI Yes, that's my opinion, too. This particular ioctl is to block the TI operation, so it should be allowed as long as it's called. TI But I vaguely remember that we discussed about it, and the current TI form is the result of that. Namely, we can call TI snd_pcm_nonblock(FALSE) explicitly before calling snd_pcm_drain(). TI Though, I prefer fixing the behavior in the core side to allow the TI blocking with this call... Any reasonable objections in mind? Any progress in including a solotion to this bug in mainstream alsa linux kernel? Has anything been done? The patch works fine for me... I think that this proposal breaks basic posix rules. Application should change blocking state itself. And non-blocking snd_pcm_drain() still makes sense - it will return state of stream (-EAGAIN - unfinished) or reset PCM state to SETUP in case when all data are played. Jaroslav - Jaroslav Kysela [EMAIL PROTECTED] Linux Kernel Sound Maintainer ALSA Project
Bug#48323: paired mysterious phenomena
clicks Infoclose loading ochrisooo jealous http://img444.imageshack.us/my.php?image=olopod9.png losershaha swatza wonder finally orLogin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#373762: Tim Strazzini
mode helping prevent Parental manage rules http://img444.imageshack.us/img444/8914/fqo4bm3.png downloaded viruses Icons nice crafted style -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406489: Request for a debian-user-slovak mailing list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: lists.debian.org, Version: unavailable; reported on 2007-01-11, Severity: normal Name: debian-user-slovak Rationale: Mailing list for slovak Debian users. Short description: Support for Debian users who speak Slovak. Long description: Support for Debian users who speak Slovak. Category: Users Subscription Policy: Open Post Policy: Open Web Archive: Yes -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFplBw8ycMYZR16dkRCAotAJ9z/1Py2xDv9Ek7+fEnY81QkcT7ogCg4h14 S0hfabAjPrduJKj/UznRozQ= =1wsI -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
