Bug#1038706: linux-image-6.1.0-9-amd64: Kernel logs "usb 3-1: 1:1: cannot set freq 48000 to ep 0x3" error on boot
Package: src:linux Version: 6.1.27-1 Severity: minor X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com Dear Maintainer, During boot the kernel logs the "usb 3-1: 1:1: cannot set freq 48000 to ep 0x3" error message. Overall, the boot process is succesful and all USB devices seem to work fine, but still this error indicates that something is wrong and is probably worth investigation. -- Package-specific info: ** Version: Linux version 6.1.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-9-amd64 root=/dev/mapper/MainVG-root ro quiet splash ** Not tainted ** Kernel log: [ 479.636601] usb 3-2: reset high-speed USB device number 3 using xhci_hcd [ 480.008306] [drm] Fence fallback timer expired on ring sdma0 [ 480.520309] [drm] Fence fallback timer expired on ring sdma0 [ 481.032305] [drm] Fence fallback timer expired on ring sdma0 [ 481.544314] [drm] Fence fallback timer expired on ring sdma0 [ 482.056324] [drm] Fence fallback timer expired on ring sdma0 [ 482.568310] [drm] Fence fallback timer expired on ring sdma0 [ 483.080313] [drm] Fence fallback timer expired on ring sdma0 [ 483.592323] [drm] Fence fallback timer expired on ring sdma0 [ 483.712314] [drm] UVD and UVD ENC initialized successfully. [ 483.812295] [drm] VCE initialized successfully. [ 483.822022] PM: hibernation: Basic memory bitmaps freed [ 483.822235] OOM killer enabled. [ 483.822236] pci_bus :05: Allocating resources [ 483.822236] Restarting tasks ... [ 483.822238] pci :04:00.0: bridge window [io 0x1000-0x0fff] to [bus 05] add_size 1000 [ 483.822242] pci :04:00.0: bridge window [mem 0x0010-0x000f 64bit pref] to [bus 05] add_size 20 add_align 10 [ 483.822244] pci :04:00.0: bridge window [mem 0x0010-0x000f] to [bus 05] add_size 20 add_align 10 [ 483.822247] pci :04:00.0: BAR 14: no space for [mem size 0x0020] [ 483.822249] pci :04:00.0: BAR 14: failed to assign [mem size 0x0020] [ 483.822251] pci :04:00.0: BAR 15: no space for [mem size 0x0020 64bit pref] [ 483.822252] pci :04:00.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [ 483.822265] pci :04:00.0: BAR 13: no space for [io size 0x1000] [ 483.822267] pci :04:00.0: BAR 13: failed to assign [io size 0x1000] [ 483.822268] pci :04:00.0: BAR 14: no space for [mem size 0x0020] [ 483.822269] pci :04:00.0: BAR 14: failed to assign [mem size 0x0020] [ 483.822270] pci :04:00.0: BAR 15: no space for [mem size 0x0020 64bit pref] [ 483.822272] pci :04:00.0: BAR 15: failed to assign [mem size 0x0020 64bit pref] [ 483.822273] pci :04:00.0: BAR 13: no space for [io size 0x1000] [ 483.822294] pci :04:00.0: BAR 13: failed to assign [io size 0x1000] [ 483.822295] pci :04:00.0: PCI bridge to [bus 05] [ 483.825046] done. [ 483.888379] PM: hibernation: hibernation exit [ 483.920467] Generic FE-GE Realtek PHY r8169-0-600:00: attached PHY driver (mii_bus:phy_addr=r8169-0-600:00, irq=MAC) [ 484.120508] r8169 :06:00.0 enp6s0: Link is Down [ 487.539407] r8169 :06:00.0 enp6s0: Link is Up - 1Gbps/Full - flow control off [ 487.539436] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 3805 board_vendor: ASUSTeK COMPUTER INC. board_name: Z170-K board_version: Rev X.0x ** Loaded modules: xt_CHECKSUM xt_MASQUERADE nft_chain_nat nf_nat bridge stp llc qrtr binfmt_misc ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_comment nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables libcrc32c nfnetlink nls_ascii nls_cp437 vfat fat intel_rapl_msr snd_hda_codec_realtek intel_rapl_common x86_pkg_temp_thermal snd_hda_codec_generic intel_powerclamp coretemp snd_hda_codec_hdmi snd_usb_audio snd_hda_intel snd_intel_dspcfg kvm_intel snd_intel_sdw_acpi snd_hda_codec snd_usbmidi_lib uvcvideo snd_hda_core snd_rawmidi kvm snd_hwdep snd_seq_device eeepc_wmi asus_wmi videobuf2_vmalloc videobuf2_memops snd_pcm videobuf2_v4l2 irqbypass platform_profile mei_hdcp videobuf2_common iTCO_wdt battery snd_timer rapl intel_pmc_bxt intel_cstate sparse_keymap videodev mei_me ledtrig_audio snd iTCO_vendor_support intel_uncore rfkill pcspkr wmi_bmof mc watchdog ee1004 mei soundcore intel_pmc_core acpi_pad evdev sg parport_pc ppdev lp parport fuse loop efi_pstore configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_crypt dm_mod hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid sd_mod t10_pi
Bug#1038701: lightdm logs "lightdm[1166]: gkr-pam: unable to locate daemon control file" error on boot
Package: lightdm Version: 1.26.0-8 Severity: minor X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com Dear Maintainer, I've noticed that on boot system logs the "lightdm[1166]: gkr-pam: unable to locate daemon control file" error message from lightdm, which indicates that there is some issue. Nevertheless, the booting process succeeds. The expectation is that such error shouldn't occur. -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled DE: Xfce Versions of packages lightdm depends on: ii adduser3.134 ii dbus 1.14.6-1 ii debconf [debconf-2.0] 1.5.82 ii libaudit1 1:3.0.9-1 ii libc6 2.36-9 ii libgcrypt201.10.1-3 ii libglib2.0-0 2.74.6-2 ii libpam-systemd [logind]252.6-1 ii libpam0g 1.5.2-6 ii libxcb11.15-1 ii libxdmcp6 1:1.1.2-3 ii lightdm-gtk-greeter [lightdm-greeter] 2.0.8-2+b1 ii lsb-base 11.6 ii sysvinit-utils [lsb-base] 3.06-4 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+23 Versions of packages lightdm suggests: ii accountsservice 22.08.8-6 ii upower 0.99.20-2 pn xserver-xephyr -- Configuration Files: /etc/lightdm/lightdm.conf changed: [LightDM] [Seat:*] greeter-hide-users=false [XDMCPServer] [VNCServer] -- debconf information: lightdm/daemon_name: /usr/sbin/lightdm * shared/default-x-display-manager: lightdm
Bug#1038627: general: Various applications log PipeWire-related errors on a Bookworm system using PulseAudio.
Package: general Severity: minor X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com Dear Maintainer, After upgrade to Bookworm, due to certain limitations of the current PipeWire implementation I had to switch to PulseAudio. The switch was done by installing pulseaudio package, deleting all PipeWire packages and finally enabling pulseaudio service on a user level. After several reboots and usage of various applications I've noticed strange errors (visible using journalctl -p 3 -xb) logged that looked as follows: "pw.conf: can't load default config client.conf: No such file or directory" Primarily this error was logged by mpv and Telegram applications. Investigation of several sources has shown that maybe creation of an empty ~/.config/pipewire/client.conf" file might fix the error. And indeed it fixed the original error, but procreated a new type of errors: that look as follows: Jun 19 07:01:41 Yura-PC xdg-desktop-portal[1768]: pw.core: 0x55d8ca82c830: can't find protocol 'PipeWire:Protocol:Native': Operation not supp> Jun 19 07:01:42 Yura-PC Telegram[1528]: pw.core: 0x7f78f6ff3d80: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 08:48:37 Yura-PC mpv[4283]: pw.core: 0x5630b5b7c9f0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 08:51:12 Yura-PC mpv[3200]: pw.core: 0x56312d870420: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 08:52:14 Yura-PC mpv[3200]: pw.core: 0x56312d7eff10: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 08:55:55 Yura-PC mpv[3200]: pw.core: 0x56312d8549b0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 08:56:19 Yura-PC mpv[3200]: pw.core: 0x56312d8845d0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:00:53 Yura-PC mpv[3200]: pw.core: 0x56312d7cc000: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:01:12 Yura-PC mpv[3200]: pw.core: 0x56312d883d40: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:03:41 Yura-PC mpv[3200]: pw.core: 0x56312d865130: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:05:15 Yura-PC mpv[3200]: pw.core: 0x56312d7fe5d0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:07:39 Yura-PC mpv[3200]: pw.core: 0x56312d857cf0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:09:31 Yura-PC mpv[3200]: pw.core: 0x56312d7f5740: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:10:56 Yura-PC mpv[3200]: pw.core: 0x56312d85e1e0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:11:50 Yura-PC mpv[3200]: pw.core: 0x56312d8837c0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:15:30 Yura-PC mpv[3200]: pw.core: 0x56312d8656a0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:16:07 Yura-PC mpv[3200]: pw.core: 0x56312d802ab0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:18:11 Yura-PC mpv[3200]: pw.core: 0x56312d861820: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:19:02 Yura-PC mpv[3200]: pw.core: 0x56312d85e270: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:20:36 Yura-PC mpv[3200]: pw.core: 0x56312d8828a0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:22:40 Yura-PC mpv[3200]: pw.core: 0x56312d7f7e40: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:32:29 Yura-PC mpv[3200]: pw.core: 0x56312d8851a0: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Jun 19 09:33:17 Yura-PC mpv[3200]: pw.core: 0x56312d8e0540: can't find protocol 'PipeWire:Protocol:Native': Operation not supported So it seems these are PipeWire-related errors logged on a system that doesn't use this audio subsystem. The expectation is that such errors aren't logged. It's worth noting that both input and output audio work fine, despite the error being logged. Best Regards, Yura
Bug#1038446: linux-image-6.1.0-9-amd64: "SGX disabled by BIOS" message is printed at boot, but SGX is set to Software Controlled in UEFI.
Package: src:linux Version: 6.1.27-1 Severity: minor Tags: upstream X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com Dear Maintainer, When system boots before the Plymouth screen is shown, it prints "SGX disabled by BIOS" message. This doesn't affect the boot process. In my BIOS/UEFI settings Software Guard Extensions are set to "Software Controlled". There are only "Software Controlled" and "Disable" options available. The situation wasn't reproducible with Bullseye. It only appeared with upgrade to Bookworm. This message shouldn't be printed if SGX is set to "Software Controlled", or, ideally, it shouldn't be printed at all. Best Regards, Yura -- Package-specific info: ** Version: Linux version 6.1.0-9-amd64 (debian-ker...@lists.debian.org) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) ** Command line: BOOT_IMAGE=/vmlinuz-6.1.0-9-amd64 root=/dev/mapper/MainVG-root ro quiet splash ** Not tainted ** Model information sys_vendor: System manufacturer product_name: System Product Name product_version: System Version chassis_vendor: Default string chassis_version: Default string bios_vendor: American Megatrends Inc. bios_version: 3805 board_vendor: ASUSTeK COMPUTER INC. board_name: Z170-K board_version: Rev X.0x ** Loaded modules: exfat xt_CHECKSUM xt_MASQUERADE nft_chain_nat nf_nat bridge stp llc qrtr ip6t_REJECT nf_reject_ipv6 xt_hl ip6_tables ip6t_rt ipt_REJECT nf_reject_ipv4 xt_LOG nf_log_syslog xt_comment nft_limit xt_limit xt_addrtype xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables libcrc32c nfnetlink binfmt_misc nls_ascii nls_cp437 vfat fat intel_rapl_msr snd_hda_codec_realtek intel_rapl_common snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi coretemp snd_hda_intel kvm_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec uvcvideo kvm snd_usb_audio eeepc_wmi snd_hda_core videobuf2_vmalloc asus_wmi snd_usbmidi_lib videobuf2_memops irqbypass snd_rawmidi videobuf2_v4l2 snd_hwdep platform_profile snd_seq_device rapl battery videobuf2_common mei_hdcp sparse_keymap snd_pcm intel_cstate iTCO_wdt ledtrig_audio snd_timer intel_pmc_bxt rfkill intel_uncore videodev iTCO_vendor_support mei_me snd watchdog pcspkr wmi_bmof ee1004 mc mei soundcore intel_pmc_core acpi_pad evdev sg parport_pc ppdev lp parport fuse loop efi_pstore configfs efivarfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic hid_logitech_hidpp dm_crypt dm_mod hid_logitech_dj hid_generic usbhid hid uas usb_storage sd_mod t10_pi crc64_rocksoft_generic crc64_rocksoft crc_t10dif crct10dif_generic crc64 amdgpu crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel sha512_ssse3 sha512_generic gpu_sched drm_buddy i2c_algo_bit drm_display_helper cec rc_core ahci drm_ttm_helper libahci ttm xhci_pci drm_kms_helper libata xhci_hcd r8169 aesni_intel drm mxm_wmi realtek usbcore crypto_simd mdio_devres scsi_mod cryptd libphy i2c_i801 i2c_smbus usb_common scsi_common fan video wmi button ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:591f] (rev 05) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05) (prog-if 00 [Normal decode]) Subsystem: ASUSTeK Computer Inc. 6th-10th Gen Core Processor PCIe Controller (x16) [1043:8694] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset F
Bug#1038445: When in full-screen mode mpv gets minimized after switching Xfce workspaces
Package: mpv Version: 0.35.1-4 Severity: normal Tags: upstream X-Debbugs-Cc: splashed_overbuilt...@simplelogin.com Dear Maintainer, The issue could be reproduced at the very least for users of Xfce desktop environment, who have the mpv player opened on one workspace in a full-screen mode. In addition, users of other distributions like Fedora Xfce might also be affected. If the user switches to a different workspace, for example, a second one and then goes back to the one where mpv is opened, the player gets minimized. The expected behavior is that the application should remain in a full-screen mode without being minimized. Best Regards, Yura -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mpv depends on: ii libarchive13 3.6.2-1 ii libasound2 1.2.8-1+b1 ii libass91:0.17.1-1 ii libavcodec-extra59 [libavcodec59] 7:5.1.3-1 ii libavdevice59 7:5.1.3-1 ii libavfilter8 7:5.1.3-1 ii libavformat59 7:5.1.3-1 ii libavutil577:5.1.3-1 ii libbluray2 1:1.3.4-1 ii libc6 2.36-9 ii libcaca0 0.99.beta20-3 ii libcdio-cdda2 10.2+2.0.1-1 ii libcdio-paranoia2 10.2+2.0.1-1 ii libcdio19 2.1.0-4 ii libdrm22.4.114-1+b1 ii libdvdnav4 6.1.1-1 ii libegl11.6.0-1 ii libgbm122.3.6-1+deb12u1 ii libjack-jackd2-0 [libjack-0.125] 1.9.21~dfsg-3 ii libjpeg62-turbo1:2.1.5-2 ii liblcms2-2 2.14-2 ii liblua5.2-05.2.4-3 ii libmujs2 1.3.2-1 ii libpipewire-0.3-0 0.3.65-3 ii libplacebo208 4.208.0-3 ii libpulse0 16.1+dfsg1-2+b1 ii librubberband2 3.1.2+dfsg0-1 ii libsdl2-2.0-0 2.26.5+dfsg-1 ii libsixel1 1.10.3-3 ii libswresample4 7:5.1.3-1 ii libswscale67:5.1.3-1 ii libuchardet0 0.0.7-1 ii libva-drm2 2.17.0-1 ii libva-wayland2 2.17.0-1 ii libva-x11-22.17.0-1 ii libva2 2.17.0-1 ii libvdpau1 1.5-2 ii libvulkan1 1.3.239.0-1 ii libwayland-client0 1.21.0-1 ii libwayland-cursor0 1.21.0-1 ii libwayland-egl11.21.0-1 ii libx11-6 2:1.8.4-2 ii libxext6 2:1.3.4-1+b1 ii libxinerama1 2:1.1.4-3 ii libxkbcommon0 1.5.0-1 ii libxpresent1 1.0.0-2+b10 ii libxrandr2 2:1.5.2-2+b1 ii libxss11:1.2.3-1 ii libxv1 2:1.0.11-1.1 ii libzimg2 3.0.4+ds1-1 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages mpv recommends: ii xdg-utils 1.1.3-4.1 ii yt-dlp 2023.03.04-1 Versions of packages mpv suggests: pn libcuda1 -- no debconf information
Bug#811578: Confetti fixed
This warnings (transformed to errors by Werror) are fixed in master branch at https://github.com/mailru/confetti/ With regards, Sokolov Yura
Bug#621081: proftpd-basic: ProFTPd cannot start in inetd/xinetd mode.
Package: proftpd-basic Version: 1.3.3a-6squeeze1 Severity: important ProFTPd cannot start in inetd/xinetd mode. in the ProFTPd configuration window select from inetd and I see output: grep: /etc/inetd.conf: No such file or directory ProFTPd warning: cannot start neither in standalone nor in inetd/xinetd mode. Check your configuration. -- System Information: Debian Release: 6.0.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages proftpd-basic depends on: ii adduser 3.112+nmu2 add and remove users and groups ii debconf 1.5.36.1 Debian configuration management sy ii debianutils 3.4 Miscellaneous utilities specific t ii libacl1 2.2.49-4 Access control list shared library ii libattr11:2.4.44-2 Extended attribute shared library ii libc6 2.11.2-10Embedded GNU C Library: Shared lib ii libcap2 1:2.19-3 support for getting/setting POSIX. ii libncurses5 5.7+20100313-5 shared libraries for terminal hand ii libpam-runtime 1.1.1-6.1Runtime support for the PAM librar ii libpam0g1.1.1-6.1Pluggable Authentication Modules l ii libssl0.9.8 0.9.8o-4squeeze1 SSL shared libraries ii libwrap07.6.q-19 Wietse Venema's TCP wrappers libra ii netbase 4.45 Basic TCP/IP networking system ii sed 4.2.1-7 The GNU sed stream editor ii ucf 3.0025+nmu1 Update Configuration File: preserv ii update-inetd4.38+nmu1inetd configuration file updater ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime proftpd-basic recommends no packages. Versions of packages proftpd-basic suggests: ii openssl 0.9.8o-4squeeze1 Secure Socket Layer (SSL) binary a pn proftpd-doc none (no description available) pn proftpd-mod-ldapnone (no description available) pn proftpd-mod-mysql none (no description available) pn proftpd-mod-odbcnone (no description available) pn proftpd-mod-pgsql none (no description available) pn proftpd-mod-sqlite none (no description available) ii xinetd [inet-superserve 1:2.3.14-7 replacement for inetd with many en -- debconf information: * shared/proftpd/inetd_or_standalone: from inetd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621081: proftpd-basic: ProFTPd cannot start in inetd/xinetd mode.
Yeah, xinetd installed. As I understand proftpd package don't have inetd in package dependencies but notes about inetd/xinetd way of installation. And after xinetd installation and dpkg-reconfigure proftpd still don't working(this looks like a bug for me :) -- Yura Beznos On Thu, Apr 7, 2011 at 9:31 AM, Francesco P. Lovergine fran...@debian.orgwrote: On Wed, Apr 06, 2011 at 04:56:31PM +0400, Yura Beznos wrote: ii update-inetd4.38+nmu1inetd configuration file updater ii xinetd [inet-superserve 1:2.3.14-7 replacement for inetd with many en Sorry I did not note that: you are on your own with xinetd configuration and checking if it is correctly done is quite tricky. The script does a reasonable check sbout that, possibly wrong. -- Francesco P. Lovergine
Bug#508982: BTS #508982: Suffered the same problem
On Sun, 22 Feb 2009 at 16:58 +0100, Andreas Hoenen wrote: Just suffered the problem with the wrong fstab description in the manual page, too. Good that this report exists, but it would be even better if the misleading description could be fixed ;-) Problem is not in wrong description, but in wrong debian packaging. mount.fuse.ntfs symlink is not included into package (only outdated mount.ntfs-fuse symlink). -- Best regards, Yura -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#336357: ntfsprogs: ntfsmount does not function
On Sat, 2005-10-29 at 13:55 -0400, Jeff Bonham wrote: Package: ntfsprogs Version: 1.11.2-3 Severity: important The ntfsmount FUSE module does not work as described in the man page. When I tried to mount a Windows XP NTFS partition with it, the following error occurred: $ sudo ntfsmount /windows -o dev=/dev/hda1 fusermount: mount failed: Invalid argument fuse_mount failed. Unmounting: WINXP hda1 mounts fine using the Linux kernel's NTFS driver. I'm using Linux 2.6.14 with the built-in FUSE support. This is the exact syntax specified in the man page. This bug appears because ntfsmount supply 'kernel_cache' option by default. But Miklos broke interface in FUSE-2.4.0, so it's no longer works. You need to upgrade to ntfsprogs-1.12.1 or supply 'no_def_options' to ntfsmount. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages ntfsprogs depends on: ii libc6 2.3.5-7GNU C Library: Shared libraries an ii libfuse2 2.4.0-1Filesystem in USErspace library ii libntfs7 1.11.2-3 library that provides common NTFS ntfsprogs recommends no packages. -- no debconf information -- Best regards, Yura -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
