Bug#1025069: pipewire: audio broken, only says Dummy Output (on plain bookworm install)
Package: pipewire-pulse Version: 0.3.65-3 Followup-For: Bug #1025069 X-Debbugs-Cc: dmitr...@gmail.com I'm confirming this issue. After upgrade from bullseye to bookworm sound in KDE disappeared. I was able to restore it after manually installing wireplumber. -- System Information: Debian Release: 12.0 APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-7-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pipewire-pulse depends on: ii init-system-helpers 1.65.2 ii pipewire 0.3.65-3 Versions of packages pipewire-pulse recommends: ii wireplumber 0.4.13-1 Versions of packages pipewire-pulse suggests: ii libspa-0.2-bluetooth 0.3.65-3 pn pulseaudio-utils -- no debconf information
Bug#1031027: libprometheus-cpp-core1.0: Library is built w/o optimization enabled
Package: libprometheus-cpp-core1.0 Version: 1.0.0-1 Severity: important X-Debbugs-Cc: dmitr...@gmail.com The CMakeList.txt of the library doesn't contain default CMAKE_BUILD_TYPE to be set to Release. Neither this variable is not set in debian/rules file. So the resulting library is build with no optimization enabled which hits performance by factor of around 2x. -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libprometheus-cpp-core1.0 depends on: ii libc6 2.31-13+deb11u5 ii libgcc-s1 10.2.1-6 ii libstdc++6 10.2.1-6 libprometheus-cpp-core1.0 recommends no packages. libprometheus-cpp-core1.0 suggests no packages. -- no debconf information
Bug#1030108: libmimalloc2.0: Build type is not specified during configure phase of packages. It kills performance.
Package: libmimalloc2.0 Version: 2.0.9+ds-1~dbp2 Severity: important X-Debbugs-Cc: dmitr...@gmail.com There is no -DCMAKE_BUILD_TYPE release in debian/rules override_dh_auto_configure target. The package is built with CMAKE_BUILD_TYPE equal to None. This renders its performance unusable - actually far more worse that even libc's malloc. I've discovered it when backported this package to bullseye and noticed that its performance is awful but local build of the same version is pretty much good. Please add this flag until bookworm is completly frozed! -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-21-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_CRAP, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libmimalloc2.0 depends on: ii libc6 2.31-13+deb11u5 libmimalloc2.0 recommends no packages. libmimalloc2.0 suggests no packages. -- no debconf information
Bug#1004290: ca-certificates: GeoTrust RSA CA 2018 intermediate certificate is missing in package
Package: ca-certificates Version: 20210119 Severity: important X-Debbugs-Cc: dmitr...@gmail.com According to Mozilla's list of included intermediate certificates https://ccadb-public.secure.force.com/mozilla/PublicAllIntermediateCerts GeoTrust RSA CA 2018 should be present in certificate store, but it is absent in ca-certificates package resulting curl to fail on many sites which are using GeoTrust certificates. -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.77 ii openssl1.1.1k-1+deb11u1 ca-certificates recommends no packages. ca-certificates suggests no packages. -- debconf information: ca-certificates/new_crts: ca-certificates/enable_crts: mozilla/ACCVRAIZ1.crt, mozilla/AC_RAIZ_FNMT-RCM.crt, mozilla/Actalis_Authentication_Root_CA.crt, mozilla/AffirmTrust_Commercial.crt, mozilla/AffirmTrust_Networking.crt, mozilla/AffirmTrust_Premium.crt, mozilla/AffirmTrust_Premium_ECC.crt, mozilla/Amazon_Root_CA_1.crt, mozilla/Amazon_Root_CA_2.crt, mozilla/Amazon_Root_CA_3.crt, mozilla/Amazon_Root_CA_4.crt, mozilla/Atos_TrustedRoot_2011.crt, mozilla/Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.crt, mozilla/Baltimore_CyberTrust_Root.crt, mozilla/Buypass_Class_2_Root_CA.crt, mozilla/Buypass_Class_3_Root_CA.crt, mozilla/CA_Disig_Root_R2.crt, mozilla/Certigna.crt, mozilla/Certigna_Root_CA.crt, mozilla/certSIGN_ROOT_CA.crt, mozilla/certSIGN_Root_CA_G2.crt, mozilla/Certum_Trusted_Network_CA_2.crt, mozilla/Certum_Trusted_Network_CA.crt, mozilla/CFCA_EV_ROOT.crt, mozilla/Chambers_of_Commerce_Root_-_2008.crt, mozilla/Comodo_AAA_Services_root.crt, mozilla/COMODO_Certification_Authority.crt, mozilla/COMODO_ECC_Certification_Authority.crt, mozilla/COMODO_RSA_Certification_Authority.crt, mozilla/Cybertrust_Global_Root.crt, mozilla/DigiCert_Assured_ID_Root_CA.crt, mozilla/DigiCert_Assured_ID_Root_G2.crt, mozilla/DigiCert_Assured_ID_Root_G3.crt, mozilla/DigiCert_Global_Root_CA.crt, mozilla/DigiCert_Global_Root_G2.crt, mozilla/DigiCert_Global_Root_G3.crt, mozilla/DigiCert_High_Assurance_EV_Root_CA.crt, mozilla/DigiCert_Trusted_Root_G4.crt, mozilla/DST_Root_CA_X3.crt, mozilla/D-TRUST_Root_Class_3_CA_2_2009.crt, mozilla/D-TRUST_Root_Class_3_CA_2_EV_2009.crt, mozilla/EC-ACC.crt, mozilla/emSign_ECC_Root_CA_-_C3.crt, mozilla/emSign_ECC_Root_CA_-_G3.crt, mozilla/emSign_Root_CA_-_C1.crt, mozilla/emSign_Root_CA_-_G1.crt, mozilla/Entrust.net_Premium_2048_Secure_Server_CA.crt, mozilla/Entrust_Root_Certification_Authority.crt, mozilla/Entrust_Root_Certification_Authority_-_EC1.crt, mozilla/Entrust_Root_Certification_Authority_-_G2.crt, mozilla/Entrust_Root_Certification_Authority_-_G4.crt, mozilla/ePKI_Root_Certification_Authority.crt, mozilla/e-Szigno_Root_CA_2017.crt, mozilla/E-Tugra_Certification_Authority.crt, mozilla/GDCA_TrustAUTH_R5_ROOT.crt, mozilla/GeoTrust_Primary_Certification_Authority_-_G2.crt, mozilla/Global_Chambersign_Root_-_2008.crt, mozilla/GlobalSign_ECC_Root_CA_-_R4.crt, mozilla/GlobalSign_ECC_Root_CA_-_R5.crt, mozilla/GlobalSign_Root_CA.crt, mozilla/GlobalSign_Root_CA_-_R2.crt, mozilla/GlobalSign_Root_CA_-_R3.crt, mozilla/GlobalSign_Root_CA_-_R6.crt, mozilla/Go_Daddy_Class_2_CA.crt, mozilla/Go_Daddy_Root_Certificate_Authority_-_G2.crt, mozilla/GTS_Root_R1.crt, mozilla/GTS_Root_R2.crt, mozilla/GTS_Root_R3.crt, mozilla/GTS_Root_R4.crt, mozilla/Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015.crt, mozilla/Hellenic_Academic_and_Research_Institutions_RootCA_2011.crt, mozilla/Hellenic_Academic_and_Research_Institutions_RootCA_2015.crt, mozilla/Hongkong_Post_Root_CA_1.crt, mozilla/Hongkong_Post_Root_CA_3.crt, mozilla/IdenTrust_Commercial_Root_CA_1.crt, mozilla/IdenTrust_Public_Sector_Root_CA_1.crt, mozilla/ISRG_Root_X1.crt, mozilla/Izenpe.com.crt, mozilla/Microsec_e-Szigno_Root_CA_2009.crt, mozilla/Microsoft_ECC_Root_Certificate_Authority_2017.crt, mozilla/Microsoft_RSA_Root_Certificate_Authority_2017.crt, mozilla/NAVER_Global_Root_Certification_Authority.crt, mozilla/NetLock_Arany_=Class_Gold=_Főtanúsítvány.crt, mozilla/Network_Solutions_Certificate_Authority.crt, mozilla/OISTE_WISeKey_Global_Root_GB_CA.crt, mozilla/OISTE_WISeKey_Global_Root_GC_CA.crt, mozilla/QuoVadis_Root_CA_1_G3.crt, mozilla/QuoVadis_Root_CA_2.crt, mozilla/QuoVadis_Root_CA_2_G3.crt, mozilla/QuoVadis_Root_CA_3.crt, mozilla/QuoVadis_Root_CA_3_G3.crt,
Bug#1004266: ca-certificates: GeoTrust Global CA certificate is again missing
Package: ca-certificates Version: 20210119 Severity: important X-Debbugs-Cc: dmitr...@gmail.com This case was once reported in #962596. Though it is marked done current package's changelog doesn't reflect any of changes reported in #962596. Broken behavior is still the same: everything works in any browser but when using CLI tool like curl verification fails. -- System Information: Debian Release: 11.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.77 ii openssl1.1.1k-1+deb11u1 ca-certificates recommends no packages. ca-certificates suggests no packages. -- debconf information: ca-certificates/enable_crts: mozilla/ACCVRAIZ1.crt, mozilla/AC_RAIZ_FNMT-RCM.crt, mozilla/Actalis_Authentication_Root_CA.crt, mozilla/AffirmTrust_Commercial.crt, mozilla/AffirmTrust_Networking.crt, mozilla/AffirmTrust_Premium.crt, mozilla/AffirmTrust_Premium_ECC.crt, mozilla/Amazon_Root_CA_1.crt, mozilla/Amazon_Root_CA_2.crt, mozilla/Amazon_Root_CA_3.crt, mozilla/Amazon_Root_CA_4.crt, mozilla/Atos_TrustedRoot_2011.crt, mozilla/Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.crt, mozilla/Baltimore_CyberTrust_Root.crt, mozilla/Buypass_Class_2_Root_CA.crt, mozilla/Buypass_Class_3_Root_CA.crt, mozilla/CA_Disig_Root_R2.crt, mozilla/Certigna.crt, mozilla/Certigna_Root_CA.crt, mozilla/certSIGN_ROOT_CA.crt, mozilla/certSIGN_Root_CA_G2.crt, mozilla/Certum_Trusted_Network_CA_2.crt, mozilla/Certum_Trusted_Network_CA.crt, mozilla/CFCA_EV_ROOT.crt, mozilla/Chambers_of_Commerce_Root_-_2008.crt, mozilla/Comodo_AAA_Services_root.crt, mozilla/COMODO_Certification_Authority.crt, mozilla/COMODO_ECC_Certification_Authority.crt, mozilla/COMODO_RSA_Certification_Authority.crt, mozilla/Cybertrust_Global_Root.crt, mozilla/DigiCert_Assured_ID_Root_CA.crt, mozilla/DigiCert_Assured_ID_Root_G2.crt, mozilla/DigiCert_Assured_ID_Root_G3.crt, mozilla/DigiCert_Global_Root_CA.crt, mozilla/DigiCert_Global_Root_G2.crt, mozilla/DigiCert_Global_Root_G3.crt, mozilla/DigiCert_High_Assurance_EV_Root_CA.crt, mozilla/DigiCert_Trusted_Root_G4.crt, mozilla/DST_Root_CA_X3.crt, mozilla/D-TRUST_Root_Class_3_CA_2_2009.crt, mozilla/D-TRUST_Root_Class_3_CA_2_EV_2009.crt, mozilla/EC-ACC.crt, mozilla/emSign_ECC_Root_CA_-_C3.crt, mozilla/emSign_ECC_Root_CA_-_G3.crt, mozilla/emSign_Root_CA_-_C1.crt, mozilla/emSign_Root_CA_-_G1.crt, mozilla/Entrust.net_Premium_2048_Secure_Server_CA.crt, mozilla/Entrust_Root_Certification_Authority.crt, mozilla/Entrust_Root_Certification_Authority_-_EC1.crt, mozilla/Entrust_Root_Certification_Authority_-_G2.crt, mozilla/Entrust_Root_Certification_Authority_-_G4.crt, mozilla/ePKI_Root_Certification_Authority.crt, mozilla/e-Szigno_Root_CA_2017.crt, mozilla/E-Tugra_Certification_Authority.crt, mozilla/GDCA_TrustAUTH_R5_ROOT.crt, mozilla/GeoTrust_Primary_Certification_Authority_-_G2.crt, mozilla/Global_Chambersign_Root_-_2008.crt, mozilla/GlobalSign_ECC_Root_CA_-_R4.crt, mozilla/GlobalSign_ECC_Root_CA_-_R5.crt, mozilla/GlobalSign_Root_CA.crt, mozilla/GlobalSign_Root_CA_-_R2.crt, mozilla/GlobalSign_Root_CA_-_R3.crt, mozilla/GlobalSign_Root_CA_-_R6.crt, mozilla/Go_Daddy_Class_2_CA.crt, mozilla/Go_Daddy_Root_Certificate_Authority_-_G2.crt, mozilla/GTS_Root_R1.crt, mozilla/GTS_Root_R2.crt, mozilla/GTS_Root_R3.crt, mozilla/GTS_Root_R4.crt, mozilla/Hellenic_Academic_and_Research_Institutions_ECC_RootCA_2015.crt, mozilla/Hellenic_Academic_and_Research_Institutions_RootCA_2011.crt, mozilla/Hellenic_Academic_and_Research_Institutions_RootCA_2015.crt, mozilla/Hongkong_Post_Root_CA_1.crt, mozilla/Hongkong_Post_Root_CA_3.crt, mozilla/IdenTrust_Commercial_Root_CA_1.crt, mozilla/IdenTrust_Public_Sector_Root_CA_1.crt, mozilla/ISRG_Root_X1.crt, mozilla/Izenpe.com.crt, mozilla/Microsec_e-Szigno_Root_CA_2009.crt, mozilla/Microsoft_ECC_Root_Certificate_Authority_2017.crt, mozilla/Microsoft_RSA_Root_Certificate_Authority_2017.crt, mozilla/NAVER_Global_Root_Certification_Authority.crt, mozilla/NetLock_Arany_=Class_Gold=_Főtanúsítvány.crt, mozilla/Network_Solutions_Certificate_Authority.crt, mozilla/OISTE_WISeKey_Global_Root_GB_CA.crt, mozilla/OISTE_WISeKey_Global_Root_GC_CA.crt, mozilla/QuoVadis_Root_CA_1_G3.crt, mozilla/QuoVadis_Root_CA_2.crt, mozilla/QuoVadis_Root_CA_2_G3.crt, mozilla/QuoVadis_Root_CA_3.crt, mozilla/QuoVadis_Root_CA_3_G3.crt, mozilla/QuoVadis_Root_CA.crt, mozilla/Secure_Global_CA.crt, mozilla/SecureSign_RootCA11.crt,
Bug#1002546: RFS: prometheus-cpp/1.0.0-4 [ITP] -- Prometheus Client Library for Modern C++
Package: sponsorship-requests Severity: wishlist X-Debbugs-Cc: dmitr...@gmail.com Dear mentors, I am looking for a sponsor for my package "prometheus-cpp": * Package name: prometheus-cpp Version : 1.0.0-4 Upstream Author : Jupp Müller * URL : https://github.com/jupp0r/prometheus-cpp * License : MIT * Vcs : [fill in URL of packaging vcs] Section : libs It builds those binary packages: libprometheus-cpp-core1.0 - Prometheus Client Library for Modern C++ libprometheus-cpp-push1.0 - Prometheus Client Library for Modern C++ libprometheus-cpp-pull1.0 - Prometheus Client Library for Modern C++ libprometheus-cpp-dev - Prometheus Client Library for Modern C++ To access further information about this package, please visit the following URL: https://mentors.debian.net/package/prometheus-cpp/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/prometheus-cpp/prometheus-cpp_1.0.0-4.dsc Changes for the initial release: prometheus-cpp (1.0.0-4) unstable; urgency=medium . * Provide static libraries with -dev package. prometheus-cpp (1.0.0-1) unstable; urgency=medium . * Initial release. Closes: #917817 Regards, -- Maksim Dmitrichenko
Bug#994940: libcurl4: curl doesn't set User-Agent header in certain cases
Package: libcurl4 Version: 7.74.0-1.3+b1 Severity: important X-Debbugs-Cc: dmitr...@gmail.com curl ignores User-Agent when sending second and further requests made via the same HTTP/2 connection. This bug was introduced in the 7.71 and fixed in 7.75 upstream. Here is commit of the fix: https://github.com/curl/curl/commit/0936ecd0ee5e3e28c098fefc9e2c0e6847cb7a82 Here is discussion of the issue: https://github.com/curl/curl/issues/6312 Please consider applying this patch into stable because many REST APIs require User-Agent to be specified. Without this fix libcurl4 in bullseye is hardly usable for heavy REST apps. -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'oldstable-proposed-updates-debug'), (500, 'oldstable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/32 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcurl4 depends on: ii libbrotli11.0.9-2+b2 ii libc6 2.31-13 ii libgssapi-krb5-2 1.18.3-6 ii libidn2-0 2.3.0-5 ii libldap-2.4-2 2.4.57+dfsg-3 ii libnghttp2-14 1.43.0-1 ii libpsl5 0.21.0-1.2 ii librtmp1 2.4+20151223.gitfa8646d.1-2+b2 ii libssh2-1 1.9.0-2 ii libssl1.1 1.1.1k-1 ii zlib1g1:1.2.11.dfsg-2 Versions of packages libcurl4 recommends: ii ca-certificates 20210119 libcurl4 suggests no packages. -- no debconf information
Bug#810295: WARNING: Serious error when reading debug info
Package: valgrind Version: 1:3.11.0-1 Followup-For: Bug #810295 Please find a debdiff in attachment. Backported from the upstream. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages valgrind depends on: ii libc6 2.22-11 ii libc6-dbg 2.22-11 Versions of packages valgrind recommends: ii gdb 7.10-1.1 ii valgrind-dbg 1:3.11.0-1 Versions of packages valgrind suggests: pn alleyoop pn kcachegrind pn valgrind-mpi pn valkyrie -- no debconf information diff -Nru valgrind-3.11.0/debian/changelog valgrind-3.11.0/debian/changelog --- valgrind-3.11.0/debian/changelog 2015-09-25 11:41:20.0 + +++ valgrind-3.11.0/debian/changelog 2016-06-19 00:01:35.0 + @@ -1,3 +1,10 @@ +valgrind (1:3.11.0-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Add 15_compressed.patch - support compressed debug info (closes: #810295) + + -- Max Dmitrichenko <dmitr...@gmail.com> Sat, 18 Jun 2016 23:32:04 + + valgrind (1:3.11.0-1) unstable; urgency=medium * New upstream release (Closes: #800013) diff -Nru valgrind-3.11.0/debian/patches/15_compressed.patch valgrind-3.11.0/debian/patches/15_compressed.patch --- valgrind-3.11.0/debian/patches/15_compressed.patch 1970-01-01 00:00:00.0 + +++ valgrind-3.11.0/debian/patches/15_compressed.patch 2016-06-19 00:19:52.0 + @@ -0,0 +1,1990 @@ +--- a/NEWS b/NEWS +@@ -36,6 +36,10 @@ + * Intel AVX2 support is more complete (64 bit targets only). On AVX2 + capable hosts, the simulated CPUID will now indicate AVX2 support. + ++* Valgrind is able to read compressed debuginfo sections in two formats: ++ - zlib ELF gABI format with SHF_COMPRESSED flag (gcc option -gz=zlib) ++ - zlib GNU format with .zdebug sections (gcc option -gz=zlib-gnu) ++ + * TOOL CHANGES + + * Memcheck: +@@ -197,6 +201,7 @@ + 269360 s390x: Fix addressing mode selection for compare-and-swap + 302630 Memcheck: Assertion failed: 'sizeof(UWord) == sizeof(UInt)' + == 326797 ++303877 valgrind doesn't support compressed debuginfo sections + 312989 ioctl handling needs to do POST handling on generic ioctls and [..] + 319274 Fix unhandled syscall: unix:410 (sigsuspend_nocancel) on OS X + 324181 mmap does not handle MAP_32BIT (handle it now, rather than fail it) +--- a/configure.ac b/configure.ac +@@ -1202,6 +1202,11 @@ + ]) + + ++# Check for ELF32/64_CHDR ++ ++AC_CHECK_TYPES([Elf32_Chdr, Elf64_Chdr], [], [], [[#include ]]) ++ ++ + # Check for PTHREAD_RWLOCK_T + + AC_MSG_CHECKING([for pthread_rwlock_t]) +@@ -2076,6 +2081,45 @@ + CFLAGS=$safe_CFLAGS + + ++# does this compiler support -g -gz=zlib ? ++ ++AC_MSG_CHECKING([if gcc accepts -g -gz=zlib]) ++ ++safe_CFLAGS=$CFLAGS ++CFLAGS="-g -gz=zlib" ++ ++AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[ ]], [[ ++ return 0; ++]])], [ ++ac_have_gz_zlib=yes ++AC_MSG_RESULT([yes]) ++], [ ++ac_have_gz_zlib=no ++AC_MSG_RESULT([no]) ++]) ++AM_CONDITIONAL(GZ_ZLIB, test x$ac_have_gz_zlib = xyes) ++CFLAGS=$safe_CFLAGS ++ ++ ++# does this compiler support -g -gz=zlib-gnu ? ++ ++AC_MSG_CHECKING([if gcc accepts -g -gz=zlib-gnu]) ++ ++safe_CFLAGS=$CFLAGS ++CFLAGS="-g -gz=zlib-gnu" ++ ++AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[ ]], [[ ++ return 0; ++]])], [ ++ac_have_gz_zlib_gnu=yes ++AC_MSG_RESULT([yes]) ++], [ ++ac_have_gz_zlib_gnu=no ++AC_MSG_RESULT([no]) ++]) ++AM_CONDITIONAL(GZ_ZLIB_GNU, test x$ac_have_gz_zlib_gnu = xyes) ++CFLAGS=$safe_CFLAGS ++ + # does this compiler support nested functions ? + + AC_MSG_CHECKING([if gcc accepts nested functions]) +@@ -3386,6 +3430,9 @@ + ]) + AM_CONDITIONAL(SOLARIS_RESERVE_SYSSTAT_ZONE_ADDR, test x$solaris_reserve_sysstat_zone_addr = xyes) + ++AC_CHECK_TYPES([Elf32_Chdr, Elf64_Chdr], [], [], [[#include ]]) ++ ++ + else + AM_CONDITIONAL(SOLARIS_SUN_STUDIO_AS, false) + AM_CONDITIONAL(SOLARIS_XPG_SYMBOLS_PRESENT, false) +--- a/coregrind/Makefile.am b/coregrind/Makefile.am +@@ -348,6 +348,7 @@ + m_debuginfo/readmacho.c \ + m_debuginfo/readpdb.c \ + m_debuginfo/storage.c \ ++ m_debuginfo/tinfl.c \ + m_debuginfo/tytypes.c \ + m_demangle/cp-demangle.c \ + m_demangle/cplus-dem.c \ +--- a/coregrind/m_debuginfo/image.c b/coregrind/m_debuginfo/image.c +@@ -45,6 +45,8 @@ + #include "priv_image.h"/* self */ + + #include "minilzo.h" ++#define TINFL_HEADER_FILE_ONLY ++#include "tinfl.c" + + /* These values (1024 entries of 8192 bytes each) gives a cache +size of 8MB. */ +@@ -53,15 +55,29 @@ + + #define CACHE_ENTRY_SIZE (1 << CACHE_ENTRY_SIZE_BITS) + ++#define COMMPRESSED_SLICE_ARRAY_GROW_SIZE 64 ++ + /* An entry in the cache. */ + typedef +struct
Bug#817046: libtinyxml2-dev: tinyxml2.h has CR-LF style endlines
Package: libtinyxml2-dev Version: 2.2.0-1 Severity: minor Dear Maintainer, Open file /usr/include/tinyxml2.h in emacs and see ^M at the end of each line. Probably dos2unix should be run as a build step of the package. -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/3 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libtinyxml2-dev depends on: ii libtinyxml2-2 2.2.0-1 libtinyxml2-dev recommends no packages. libtinyxml2-dev suggests no packages. -- no debconf information
Bug#659579: fglrx-source: Building kernel module conficts with binutils-gold package
Package: fglrx-source Version: 1:12-1-1~bpo60+1 Severity: serious Justification: fails to build from source I had binutils-gold packages installed and this was the reason that kernel module failed to build on my machine. -- Package-specific info: VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Device 68ba DRM and fglrx Informations from dmesg: [0.00] No AGP bridge found [0.381979] Linux agpgart interface v0.103 [ 2147.075957] [fglrx] Maximum main memory to use for locked dma buffers: 7771 MBytes. [ 2147.076077] [fglrx] vendor: 1002 device: 68ba count: 1 [ 2147.076565] [fglrx] ioport: bar 4, base 0xde00, size: 0x100 [ 2147.076984] [fglrx] Kernel PAT support is enabled [ 2147.077000] [fglrx] module loaded - fglrx 8.93.4 [Dec 5 2011] with 1 minors [ 2147.289792] fglrx_pci :01:00.0: irq 26 for MSI/MSI-X [ 2147.290297] [fglrx] Firegl kernel thread PID: 20316 [ 2147.290345] [fglrx] Firegl kernel thread PID: 20317 [ 2147.290390] [fglrx] Firegl kernel thread PID: 20318 [ 2147.290469] [fglrx] IRQ 26 Enabled [ 2147.379449] [fglrx] Gart USWC size:1280 M. [ 2147.379452] [fglrx] Gart cacheable size:508 M. [ 2147.379456] [fglrx] Reserved FB block: Shared offset:0, size:100 [ 2147.379458] [fglrx] Reserved FB block: Unshared offset:f8fd000, size:403000 [ 2147.379460] [fglrx] Reserved FB block: Unshared offset:3fff4000, size:c000 [ 8429.318387] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [ 8429.326881] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [ 8429.335106] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [49696.005410] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [161199.552175] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [161199.559359] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [162970.184682] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [223202.704421] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [223214.981467] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [223503.733455] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 [223528.350521] Assertion failed in ../../../../../../../../drivers/2d/lnx/fgl/drm/kernel/hal_evergreen.c at line: 64 Xorg X server configuration file status: -rw-r--r-- 1 root root 684 Feb 9 23:55 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: Section ServerLayout Identifier aticonfig Layout Screen 0 aticonfig-Screen[0]-0 0 0 EndSection Section Module EndSection Section Monitor Identifier aticonfig-Monitor[0]-0 Option VendorName ATI Proprietary Driver Option ModelName Generic Autodetecting Monitor Option DPMS true EndSection Section Device Identifier aticonfig-Device[0]-0 Driver fglrx BusID PCI:1:0:0 EndSection Section Screen Identifier aticonfig-Screen[0]-0 Device aticonfig-Device[0]-0 Monitoraticonfig-Monitor[0]-0 DefaultDepth 24 SubSection Display Viewport 0 0 Depth 24 EndSubSection EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 16748 Oct 2 2010 /var/log/Xorg.3.log -rw-r--r-- 1 root root 28129 Dec 17 2010 /var/log/Xorg.2.log -rw-r--r-- 1 root root 48147 Feb 12 13:25 /var/log/Xorg.1.log -rw-r--r-- 1 root root 44469 Feb 12 13:25 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 3.0.0-1-amd64 x86_64 Debian Current Operating System: Linux cuprum 2.6.32-5-amd64 #1 SMP Mon Jan 16 16:22:28 UTC 2012 x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=UUID=b4bd038d-bc4c-4c24-bb57-c696cc6f17b5 ro Build Date: 29 October 2011 06:58:14PM xorg-server 2:1.7.7-14 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Feb 12 13:23:24 2012 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (==) ServerLayout aticonfig Layout (**)
Bug#657835: libc6: libc deadlocks in child process after fork
Package: libc6 Version: 2.11.3-2 Severity: important One thread of multithreaded application calls fork(). According to the POSIX standard only that thread which called fork() would present in the child process. But the state of all mutexes, condvars and other objects are copied into the child process as is and should be reinitialized. A call for gmtime_r() from the user applications will lock internal libc lock __tzset_lock (defined in time/tzset.c). If one thread was calling gmtime_r() while another thread was calling fork(), this lock is copied into the child process in the locked state. So the first call of the child process for gmtime_r() will deadlock it. Apparently fork() implementation should have reset the state of all internal mutexes in the child process before returning control to it. This bug still applies to the head revision of glibc and eglibc. May be there are other places inside of libc which are subject to the same behaviour. -- System Information: Debian Release: 6.0.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libc6 depends on: ii libc-bin 2.11.3-2 Embedded GNU C Library: Binaries ii libgcc1 1:4.4.5-8 GCC support library libc6 recommends no packages. Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.36.1 Debian configuration management sy ii glibc-doc 2.11.3-2 Embedded GNU C Library: Documentat ii locales 2.11.3-2 Embedded GNU C Library: National L -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#657835: libc6: libc deadlocks in child process after fork
This is the stack trace of a deadlocked child: #0 __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97 #1 0x00346929c08d in _L_lock_2164 () at tzset.c:138 #2 0x00346929be47 in __tz_convert (timer=0x346959da74, use_localtime=0, tp=0x7f7a25211990) at tzset.c:619 #3 0x7f7a2a1ff2a0 in DateTime::now () at Sources/DateTime.cpp:174 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651912: sandboxing-related renderer crash (Aw, snap) when loading NSS modules
Jonathan Nieder wrote: I'm kind of surprised that this only started happening with chromium 15, though --- chromium 14 should have already been affected. Do you know what upgrade triggered this on your machine? Was it a chromium upgrade or an nss one? I can assure you that this bug also affects chromium 14 at least 14.0.835.202~r103287-1. I've tried to backport it on squeezy but got the same bug. -- Max -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#506713: Will the fix go to lenny?
Ok. Seems that bug is fixed in experimental. Two questions. 1) Will this version be uploaded to unstable and then to testing before lenny is released? 2) According to Ben, any library on SPARC is a subject to this bug. I think it is rather hard to create a list of libraries which have functions which return structures and refer to the global data. So, potentially every library can suffer from this. Will all libraries be recompiled due to this bug? P.S.: Please add me on the CC-list for further messages. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490999:
* When a newer compiler package is available for a distribution, is everything rebuilt with it? No. But this is definitely non-sense. IIRC potentially every library is a subject to be affected by the compiler's bug. The fact that other libs don't cause such a destructive behavior (as Qt with kicker) is just a matter of luck. Personally I noticed that Konqueror on sparc is also VERY unstable. Every third site opened by it crashes the Konqueror (or KJS). This is not reproducable on i386. So, IMHO, this is somehow related to this bug. I think that investigate weather each crash is related to compiler's bug or not is quite expensive an ineffective task. I think that everything should be recompiled. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500358: Fix found
2008/11/11, Bastian Blank [EMAIL PROTECTED]: Go on and read the discussion of this bug if you really interested why these patches differ. You want something from us. Also the bugreport reads itself as two different bugs, which does not make it easier to understand. Bastian, what should I do? Forward you all emails from the bug tracker? Or copy-paste the contents explaning why these two patches differ? I agree with you that it's a bit hard to follow the bug discussion, but this is probaly issue of the bug tracker, not mine. I also had the same problem when I started to search a fix. I don't want anything from you except from what you (the Debian Team) declare as your target - a well-tested, safe and working distro. With working X on SPARC. I did testing, writing the patch, again testing and posting all the results to the bug tracker. My soul is clear. As a programmer, I dream about such perfect users of my products. But what I see now is DD's fetish in arguing and not fixing the bugs. It seems to me that discussion to fix or not to fix became bigger than actual discussion of thing related to the bug. And you don't even bother to tell us why you made such decision. You simply tell us that patch is not fine. No further discussion, no suggestion, no interest to the problem. Leave it as it is. The Wall. In short, the last patch is the first patch merged with Gaudenz's patch which revert changes of SPARC PCI in 2.6.26 which breaks xserver-xorg-video-ati package. The first patch is fine. The revert is not. Well... The revert fixes X server's bug which exposed on 2.6.26 but works fine on previous kernel. New X server doesn't suffer from it and works on both pre-2.6.26 kernels and the new ones, but backporting this fix to the lenny's X server is very complicated task, AFAIK. So we see, that a well-written code works perfectly everywhere. And this should point us to the statement, that the revert doesn't break anything except buggy programs, like lenny's version of X. But buggy programs which deals with PCI in userspace are rare animals. And most of them, I think are not so important as X. A good question why you should care for X's bugs while being a kernel maintainer. But if religion doesn't allow you to include this patch then go on. I think most users will be excited if they know that during testing there was a fix for getting this thing work, but some maintainer saw that patch as not fine enough. This will serve a good service for the Debian reputation. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500358: Fix found
It is the decision of the maintainer if nothing else matches. Ok. Who is the maintainer? NMUing a properly maintained package without action from the CTTE is also a no-go. Sorry, I'm not a DD and I'm very bad in your politics and burocracy. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5769907ade8dda7002b304c03ef9e4ee5c1e0821 This is a different patch then http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=102;filename=sparc_fix_for_debian.patch;att=1;bug=500358 Go on and read the discussion of this bug if you really interested why these patches differ. In short, the last patch is the first patch merged with Gaudenz's patch which revert changes of SPARC PCI in 2.6.26 which breaks xserver-xorg-video-ati package. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500358: Fix found
2008/11/9 Bastian Blank [EMAIL PROTECTED]: OK, since there was no opposition and there is still no explaination on why this bug was donwgraded in the first place I'm upgrading it back to the initial severity. There is only a small fraction of machines affected, so this is not RC. This is not a PC case where one can assemble some unique set of components which will not work together well. SPARC is a traditionally brand architecture. This case affects Ultra 5 and may be several other workstation. So if something doesn't function on one box it doesn't function on a whole generation of boxes. I think this is quite a big part of all Debian SPARC users. And if SPARC is qualified for release then this is definitely RC. And do not hesitate to use common sense. Refusal of fixing the bug should be made only if you are afraid of breaking something else. This patch targets only SPARC. It has absolutely no influence on other archs, so it won't break anything else even in the worst case. I fail to find anything near this patch in upstream (Linus' tree), which would be the first target. So please provide commit IDs along with patches. If you want to force us to apply patches which does not follow our guidelines, you have to ask CTTE. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5769907ade8dda7002b304c03ef9e4ee5c1e0821 -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504656: xserver-xorg-input-synaptics: Stops working after logoff
2008/11/6, Julien Cristau [EMAIL PROTECTED]: Actually, it works just fine here, so that justification seems wrong. You didn't send your config or log, though, so it's hard to tell. Indeed. It works. This behavior seems to be linked with similar evdev bug because now with new evdev driver synaptics works well. I think bug can be closed now. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504536:
Synaptics driver on my laptop also has the same bug. In this light, I suspect that X server input layer introduces some change which breaks input drivers. Can someone with more detailed knowledge of X investigate this problem? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504656: xserver-xorg-input-synaptics: Stops working after logoff
Package: xserver-xorg-input-synaptics
Version: 0.14.7~git20070706-4~dmitrmax.1
Severity: grave
Tags: patch
Justification: renders package unusable
Driver forgets to ungrab the event device so the next time it is grabbed EBUSY
is returned.
This happens e.g. when I logoff from KDE session and return to KDM screen. Only
restarting
the X server helps.
Bellow patch that fixes the problem.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg-input-synaptics depends on:
ii libc6 2.7-15 GNU C Library: Shared libraries
ii libx11-6 2:1.1.5-2 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxi62:1.1.3-1 X11 Input extension library
ii xserver-xorg-core 2:1.4.2-7 Xorg X server - core server
xserver-xorg-input-synaptics recommends no packages.
Versions of packages xserver-xorg-input-synaptics suggests:
pn gsynaptics | ksynaptics | qsy none (no description available)
-- no debconf information
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg-input-synaptics depends on:
ii libc6 2.7-15 GNU C Library: Shared libraries
ii libx11-6 2:1.1.5-2 X11 client-side library
ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar
ii libxi62:1.1.3-1 X11 Input extension library
ii xserver-xorg-core 2:1.4.2-7 Xorg X server - core server
xserver-xorg-input-synaptics recommends no packages.
Versions of packages xserver-xorg-input-synaptics suggests:
pn gsynaptics | ksynaptics | qsy none (no description available)
-- no debconf information
--- xfree86-driver-synaptics-0.14.7~git20070706.orig/eventcomm.c
+++ xfree86-driver-synaptics-0.14.7~git20070706/eventcomm.c
@@ -58,6 +58,16 @@
static void
EventDeviceOffHook(LocalDevicePtr local)
{
+SynapticsPrivate *priv = (SynapticsPrivate *) (local-private);
+
+if (priv-synpara-grab_event_device) {
+ int ret;
+ SYSCALL(ret = ioctl(local-fd, EVIOCGRAB, (pointer)0));
+ if (ret 0) {
+ xf86Msg(X_WARNING, %s can't ungrab event device, errno=%d\n,
+ local-name, errno);
+ }
+}
}
static void
Bug#490999: kicker: Confirmed
Package: kicker Version: 4:3.5.9.dfsg.1-5 Followup-For: Bug #490999 I have just the same situation. Kicker dies either silently or causing a KCrash to appear. Latter case can produce a crash report but every time this report is different and mostly contains stack corruption. So, the kicker is totally unusable on sparc. Since it is one of the main KDE's component, I think this is RC-bug. I would gladly help to debug this. But I'm very unfamiliar with KDE. Running kicker under gdb is meanless because every time it finishes successfuly, but kicker dies somewhere outside of gdb. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: sparc (sparc64) Kernel: Linux 2.6.26-pcifix Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kicker depends on: ii kdebase-data 4:3.5.9.dfsg.1-5shared data files for the KDE base ii kdelibs4c2a 4:3.5.9.dfsg.1-6+b1 core libraries and binaries for al ii libc62.7-15 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1 GCC support library ii libkonq4 4:3.5.9.dfsg.1-5core libraries for Konqueror ii libqt3-mt3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libstdc++6 4.3.2-1 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.5-2 X11 client-side library ii libxau6 1:1.0.3-3 X11 authorisation library ii libxcomposite1 1:0.4.0-3 X11 Composite extension library ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio ii libxrender1 1:0.9.4-2 X Rendering Extension client libra kicker recommends no packages. Versions of packages kicker suggests: ii khelpcente 4:4.0.0.really.3.5.9.dfsg.1-5 help center for KDE pn kicker-app none(no description available) pn menu none(no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504537: xserver-xorg: X server eats CPU on sparc
Package: xserver-xorg Version: 1:7.3+18 Severity: normal X server eats 10-20% CPU in idle. It wasn't so on etch. Any thoughts how to diagnose the reason are appreciated. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Ноя 4 17:15 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1740488 Окт 1 21:33 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 3589 Ноя 5 00:48 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc # FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic # FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled # FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled # FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 # FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi # FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi # FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc # Loaddri Loadextmod Loadfreetype # Loadglx # Loadint10 Loadvbe # Loadcfb # Loadcfb32 EndSection Section InputDevice Identifier Generic Keyboard Driver evdev Option CoreKeyboard Option Device/dev/input/event0 Option XkbRules xorg Option XkbModel evdev Option XkbLayout us,ru Option XkbOptionsaltwin:meta_win EndSection Section InputDevice Identifier Configured Mouse Driver evdev Option Device/dev/input/event1 Option CorePointer #Option Physusb-:02:01.1-1/input0 EndSection Section Device Identifier Driver mach64 # Option UseFBDev true Option NoAccel true # Option NoLinear true EndSection Section Monitor Identifier Option DPMS HorizSync 30-96 VertRefresh 50-150 DisplaySize 304.8 228.6 # This will make [EMAIL PROTECTED] ModeLine1152x864 144.0 1152 1200 1344 1500 864 870 880 960 EndSection Section Screen Identifier Default Screen Device Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1152x864 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Generic Keyboard InputDevice
Bug#490999: kicker: Confirmed
Thanks Modestas! Running kicker --nofork under gdb produces the same crash with SIGBUS. Tested several times - backtrace doesn't differ except for object addresses. GDB's backtrace is attached. What's next? Is there a way to build only kicker from sources? Not necessary to build a package. Rebuilding the whole kdebase on my sparc will last 6-10 hours :( -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504536: xserver-xorg: No input possible after log off on sparc
Package: xserver-xorg Version: 1:7.3+18 Severity: normal After I log off from KDE, I get back to the kdm login screen but no input is possible. I have to switch to the VT 1 (this works) and restart kdm to log in again. Last lines of Xorg.log makes me to think that it is not KDM's bug. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Ноя 4 17:15 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1740488 Окт 1 21:33 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 3589 Ноя 5 00:48 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc # FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic # FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled # FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled # FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 # FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi # FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi # FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc # Loaddri Loadextmod Loadfreetype # Loadglx # Loadint10 Loadvbe # Loadcfb # Loadcfb32 EndSection Section InputDevice Identifier Generic Keyboard Driver evdev Option CoreKeyboard Option Device/dev/input/event0 Option XkbRules xorg Option XkbModel evdev Option XkbLayout us,ru Option XkbOptionsaltwin:meta_win EndSection Section InputDevice Identifier Configured Mouse Driver evdev Option Device/dev/input/event1 Option CorePointer #Option Physusb-:02:01.1-1/input0 EndSection Section Device Identifier Driver mach64 # Option UseFBDev true Option NoAccel true # Option NoLinear true EndSection Section Monitor Identifier Option DPMS HorizSync 30-96 VertRefresh 50-150 DisplaySize 304.8 228.6 # This will make [EMAIL PROTECTED] ModeLine1152x864 144.0 1152 1200 1344 1500 864 870 880 960 EndSection Section Screen Identifier Default Screen Device Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1152x864 1024x768 800x600 640x480 EndSubSection EndSection Section ServerLayout Identifier Default
Bug#504536: Fix available
It happens that evdev 2.0 is brain damaged. It opens required file
descriptor once X server is started, closes it after logoff and never
opens it again. So evdev is hardly usable on all archs.
Patch to fix this is attached. I'm going to raise this bug severity to RC.
--
Max
diff -urpN xserver-xorg-input-evdev-2.0.3/src/evdev.c xserver-xorg-input-evdev-2.0.3-fixed/src/evdev.c
--- xserver-xorg-input-evdev-2.0.3/src/evdev.c 2008-11-05 04:20:25.0 +0300
+++ xserver-xorg-input-evdev-2.0.3-fixed/src/evdev.c 2008-11-05 04:24:12.0 +0300
@@ -831,6 +831,7 @@ EvdevProc(DeviceIntPtr device, int what)
{
InputInfoPtr pInfo;
EvdevPtr pEvdev;
+const char* devicePath = 0;
pInfo = device-public.devicePrivate;
pEvdev = pInfo-private;
@@ -838,6 +839,26 @@ EvdevProc(DeviceIntPtr device, int what)
switch (what)
{
case DEVICE_INIT:
+devicePath = xf86CheckStrOption(pInfo-conf_idev-commonOptions, Path, NULL);
+
+if (!devicePath)
+devicePath = xf86CheckStrOption(pInfo-conf_idev-commonOptions, Device, NULL);
+
+if (!devicePath) {
+xf86Msg(X_ERROR, %s: No device specified.\n, pInfo-name);
+return !Success;
+}
+
+do {
+pInfo-fd = open(devicePath, O_RDWR, 0);
+}
+while (pInfo-fd 0 errno == EINTR);
+
+if(pInfo-fd 0) {
+xf86Msg(X_ERROR, Unable to open evdev device \%s\.\n, devicePath);
+return !Success;
+}
+
return EvdevInit(device);
case DEVICE_ON:
@@ -854,17 +875,21 @@ EvdevProc(DeviceIntPtr device, int what)
break;
case DEVICE_OFF:
-if (!pEvdev-kernel24 ioctl(pInfo-fd, EVIOCGRAB, (void *)0))
-xf86Msg(X_WARNING, %s: Release failed (%s)\n, pInfo-name,
-strerror(errno));
-xf86RemoveEnabledDevice(pInfo);
-EvdevMBEmuFinalize(pInfo);
- device-public.on = FALSE;
- break;
-
case DEVICE_CLOSE:
- xf86Msg(X_INFO, %s: Close\n, pInfo-name);
- close(pInfo-fd);
+if(device-public.on == TRUE) {
+if (!pEvdev-kernel24 ioctl(pInfo-fd, EVIOCGRAB, (void *)0))
+xf86Msg(X_WARNING, %s: Release failed (%s)\n, pInfo-name,
+strerror(errno));
+xf86RemoveEnabledDevice(pInfo);
+EvdevMBEmuFinalize(pInfo);
+device-public.on = FALSE;
+}
+
+if(what == DEVICE_CLOSE) {
+xf86Msg(X_INFO, %s: Close\n, pInfo-name);
+close(pInfo-fd);
+pInfo-fd = -1;
+}
break;
}
@@ -1071,6 +1096,9 @@ EvdevPreInit(InputDriverPtr drv, IDevPtr
return NULL;
}
+close(pInfo-fd);
+pInfo-fd = -1;
+
return pInfo;
}
Bug#500358:
Proposed patch. Explanations here [1].
[1] http://marc.info/?l=linux-kernelm=122545873605649w=2
--
Max
diff -uprN linux-source-2.6.26/arch/sparc64/kernel/pci.c linux-source-2.6.26.pci-fixed/arch/sparc64/kernel/pci.c
--- linux-source-2.6.26/arch/sparc64/kernel/pci.c 2008-07-14 01:51:29.0 +0400
+++ linux-source-2.6.26.pci-fixed/arch/sparc64/kernel/pci.c 2008-10-31 01:23:54.0 +0300
@@ -1017,6 +1017,7 @@ static int __pci_mmap_make_offset(struct
for (i = 0; i = PCI_ROM_RESOURCE; i++) {
struct resource *rp = pdev-resource[i];
+ resource_size_t aligned_end;
/* Active? */
if (!rp-flags)
@@ -1034,8 +1035,15 @@ static int __pci_mmap_make_offset(struct
continue;
}
+ /* Align the resource end to the next page address.
+ * PAGE_SIZE intentionally added instead of (PAGE_SIZE - 1),
+ * because actually we need the address of the next byte
+ * after rp-end.
+ */
+ aligned_end = (rp-end + PAGE_SIZE) PAGE_MASK;
+
if ((rp-start = user_paddr)
- (user_paddr + user_size) = (rp-end + 1UL))
+ (user_paddr + user_size) = aligned_end)
break;
}
Bug#500358: Ответ: xserver-xorg-core: xserver-xorg 1.5 has the same problem
2008/10/29, Gaudenz Steinlin [EMAIL PROTECTED]: Hi Max Thanks for testing. IMO the situation is now much more clear. I'm happy that you confirmed that the patched kernel fixes the problem with the X server in lenny. Read carefully, Gaudenz. Patched kernel fixes only driver misbehaviour caused by INVALID MEM ALLOCATION. But then lenny driver fails with the other (or same) issue - it fails to mmap one of the PCI regions. The same result could be reproduced with experimental driver on following kernels: 1) etchnhalf 2.6.24 2) lenny's 2.6.26 3) your 2.6.26 Since experimental driver is more generous with logs, I conclude that in both drivers the problem PCI-region is MMIO, i.e. region 2. Not sure where the problem is, but I think it is the kernel, because I traced the mmapping codel in the libpciaccess and found out that mmap system call returns EINVAL, though the arguments are pretty correct. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500358: xserver-xorg-core: Patched kernel doesn't help
Package: xserver-xorg-core Version: 2:1.4.2-7 Followup-For: Bug #500358 Indeed, the Gaudenz's kernel helps to get rid of INVALID MEM ALLOCATION messages in the log. But the final result is that last lines of log change from: (WW) MACH64: Mach64 in slot 1:2:0 could not be detected! (II) UnloadModule: mach64 (EE) Screen(s) found, but none have a usable configuration Fatal server error: no screens found to: Fatal server error: xf86MapDomainMem(): mmap() failure P.S.: Tested also with 2.6.24-etchnhalf.1 kernel. The same result :( -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500358: xserver-xorg-core: xserver-xorg 1.5 has the same problem
Package: xserver-xorg-core Version: 2:1.5.2-1 Followup-For: Bug #500358 I've installed the xserver-xorg 1.5 and mach64 driver from experimental and tested it with: 1) Current lenny's kernel 2) Gaudenz's patched kernel 3) etchnhalf kernel (2.6.24) All the tests have the same negative result. Log attached. So, I see current situation in this light: 1) There is a regression or incompatible modification in current lenny's kernel that hits current lenny's mach64 driver on sparc64. 2) There is a regression in both lenny and expiremental mach64 driver. It is somehow related to mmaping the aperture. It appears: a) for lenny's version: only when kernel regression fixed b) for experimental version: always. -- Max -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Фев 18 2007 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1636752 Окт 12 16:38 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:02.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 3782 Окт 29 02:11 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the /etc/X11/xorg.conf manual page. # (Type man /etc/X11/xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section Files FontPath/usr/share/fonts/X11/misc # FontPath/usr/X11R6/lib/X11/fonts/misc FontPath/usr/share/fonts/X11/cyrillic # FontPath/usr/X11R6/lib/X11/fonts/cyrillic FontPath/usr/share/fonts/X11/100dpi/:unscaled # FontPath/usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath/usr/share/fonts/X11/75dpi/:unscaled # FontPath/usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath/usr/share/fonts/X11/Type1 # FontPath/usr/X11R6/lib/X11/fonts/Type1 FontPath/usr/share/fonts/X11/100dpi # FontPath/usr/X11R6/lib/X11/fonts/100dpi FontPath/usr/share/fonts/X11/75dpi # FontPath/usr/X11R6/lib/X11/fonts/75dpi # path to defoma fonts FontPath/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType EndSection Section Module Loadi2c Loadbitmap Loadddc Loadextmod Loadfreetype Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver evdev Option CoreKeyboard Option evBits +1 Option keyBits ~1-255 ~352-511 Option Pass3 Option XkbRules xorg Option XkbModel evdev Option XkbLayout us,ru Option XkbOptionsaltwin:meta_win EndSection Section InputDevice Identifier Configured Mouse Driver evdev Option evBits +1-2 Option keyBits ~272-287 Option relBits ~0-2 ~6 ~8 Option Pass3 Option CorePointer #Option Physusb-:02:01.1-1/input0 EndSection Section Device Identifier Driver mach64 # Option UseFBDev true Option NoAccel true Option NoLinear true EndSection Section Monitor Identifier Option DPMS HorizSync 30-96 VertRefresh 50-150 DisplaySize 304.8 228.6 # This will make [EMAIL PROTECTED] ModeLine1152x864 144.0 1152 1200 1344 1500 864 870 880 960 EndSection Section Screen Identifier Default Screen Device Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1152x864 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1152x864 1024x768 800x600 640x480
Bug#497971: May be a patch will help
Bastian, Xavier is right. Japan and other folks will suffer from this solution. 1) Either this dirty fix shall be desribed in the release notes of Lenny with BIG LETTERS. 2) Or I can (I believe) provide a patch that will create new Debian regulatory domain for mac80211 cards which will be a superset of all regulatory domains. Sure, this is not correct from political point of view, but anyway this limitation is too artificial. What do you think about the second solution? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497971: Proposed patch
Here is the patch that will help.
diff -uprN linux-source-2.6.26/net/wireless/reg.c /usr/src/linux-source-2.6.26/net/wireless/reg.c
--- linux-source-2.6.26/net/wireless/reg.c 2008-09-24 14:13:39.0 +0400
+++ /usr/src/linux-source-2.6.26/net/wireless/reg.c 2008-09-30 10:55:38.0 +0400
@@ -29,7 +29,7 @@
#include net/wireless.h
#include core.h
-static char *ieee80211_regdom = EU;
+static char *ieee80211_regdom = DEB;
module_param(ieee80211_regdom, charp, 0444);
MODULE_PARM_DESC(ieee80211_regdom, IEEE 802.11 regulatory domain code);
@@ -50,6 +50,20 @@ struct ieee80211_regdomain {
#define RANGE_PWR(_start, _end, _pwr, _ag, _flags) \
{ _start, _end, _pwr, _ag, _flags }
+static const struct ieee80211_channel_range ieee80211_DEB_channels[] = {
+ /* IEEE 802.11b/g, channels 1..14 */
+ RANGE_PWR(2412, 2484, 20, 6, 0),
+ /* IEEE 802.11a, channels 34..48 */
+ RANGE_PWR(5170, 5240, 20, 6, IEEE80211_CHAN_PASSIVE_SCAN),
+ /* IEEE 802.11a, channels 48..64 */
+ RANGE_PWR(5240, 5320, 23, 6, IEEE80211_CHAN_NO_IBSS |
+ IEEE80211_CHAN_RADAR),
+ /* IEEE 802.11a, channels 100..140 */
+ RANGE_PWR(5500, 5700, 30, 6, IEEE80211_CHAN_NO_IBSS |
+ IEEE80211_CHAN_RADAR),
+ /* IEEE 802.11a, channels 149..165, outdoor */
+ RANGE_PWR(5745, 5825, 30, 6, 0),
+};
/*
* Ideally, in the future, these definitions will be loaded from a
@@ -108,6 +122,7 @@ static const struct ieee80211_regdomain
REGDOM(US),
REGDOM(JP),
REGDOM(EU),
+ REGDOM(DEB)
};
Bug#495708: linux-image-2.6.26-1-686: Kernel 2.6.26 seems to be not affected by this bug
Package: linux-image-2.6.26-1-686 Followup-For: Bug #495708 Bug can now be closed, I think. -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Aug 28 12:00:54 UTC 2008 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.26-1-686 root=/dev/mapper/lvm0-root ro ** Not tainted ** Kernel log: [ 13.199577] EXT3-fs: mounted filesystem with ordered data mode. [ 13.216113] kjournald starting. Commit interval 5 seconds [ 13.216210] EXT3 FS on dm-1, internal journal [ 13.216210] EXT3-fs: mounted filesystem with ordered data mode. [ 15.152015] r8169: eth0: link down [ 17.419450] lp: driver loaded but no devices found [ 17.520176] ppdev: user-space parallel port driver [ 18.318966] NET: Registered protocol family 10 [ 18.323149] lo: Disabled Privacy Extensions [ 18.323149] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 19.353894] pcmcia: Detected deprecated PCMCIA ioctl usage from process: discover. [ 19.353894] pcmcia: This interface will soon be removed from the kernel; please expect breakage unless you upgrade to new tools. [ 19.353894] pcmcia: see http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for details. [ 19.913835] warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use) [ 22.212771] Bluetooth: L2CAP ver 2.9 [ 22.212904] Bluetooth: L2CAP socket layer initialized [ 22.323287] Bluetooth: RFCOMM socket layer initialized [ 22.323287] Bluetooth: RFCOMM TTY layer initialized [ 22.323287] Bluetooth: RFCOMM ver 1.8 [ 22.628162] ACPI: PCI Interrupt :04:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 22.628162] PM: Writing back config space on device :04:00.0 at offset 1 (was 12, writing 16) [ 22.628162] firmware: requesting iwlwifi-4965-1.ucode [ 22.927299] Registered led device: iwl-phy0:radio [ 22.927299] Registered led device: iwl-phy0:assoc [ 22.927299] Registered led device: iwl-phy0:RX [ 22.927299] Registered led device: iwl-phy0:TX [ 22.937825] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 70.089922] wlan0: Initial auth_alg=0 [ 70.089922] wlan0: authenticate with AP 00:13:49:c9:b7:76 [ 70.292779] wlan0: authenticate with AP 00:13:49:c9:b7:76 [ 70.294039] wlan0: RX authentication from 00:13:49:c9:b7:76 (alg=0 transaction=2 status=0) [ 70.294039] wlan0: authenticated [ 70.294039] wlan0: associate with AP 00:13:49:c9:b7:76 [ 70.296085] wlan0: RX AssocResp from 00:13:49:c9:b7:76 (capab=0x411 status=0 aid=1) [ 70.296095] wlan0: associated [ 70.296126] wlan0: switched to short barker preamble (BSSID=00:13:49:c9:b7:76) [ 70.311039] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 73.541401] padlock: VIA PadLock not detected. [ 81.018569] wlan0: no IPv6 routers present [ 98.846415] wlan0: no IPv6 routers present [ 7612.478839] wlan0: RX disassociation from 00:13:49:c9:b7:76 (reason=16) [ 7612.478852] wlan0: disassociated [ 7613.477350] wlan0: associate with AP 00:13:49:c9:b7:76 [ 7613.479235] wlan0: RX deauthentication from 00:13:49:c9:b7:76 (reason=6) [ 7613.479246] wlan0: deauthenticated [ 7614.477319] wlan0: authenticate with AP 00:13:49:c9:b7:76 [ 7614.478799] wlan0: RX authentication from 00:13:49:c9:b7:76 (alg=0 transaction=2 status=0) [ 7614.478811] wlan0: authenticated [ 7614.478818] wlan0: associate with AP 00:13:49:c9:b7:76 [ 7614.480895] wlan0: RX ReassocResp from 00:13:49:c9:b7:76 (capab=0x411 status=0 aid=1) [ 7614.480906] wlan0: associated [ 7614.480932] wlan0: switched to short barker preamble (BSSID=00:13:49:c9:b7:76) [11334.721091] wlan0: RX disassociation from 00:13:49:c9:b7:76 (reason=16) [11334.721103] wlan0: disassociated [11335.724577] wlan0: associate with AP 00:13:49:c9:b7:76 [11335.726497] wlan0: RX deauthentication from 00:13:49:c9:b7:76 (reason=6) [11335.726508] wlan0: deauthenticated [11336.726859] wlan0: authenticate with AP 00:13:49:c9:b7:76 [11336.728340] wlan0: RX authentication from 00:13:49:c9:b7:76 (alg=0 transaction=2 status=0) [11336.728352] wlan0: authenticated [11336.728359] wlan0: associate with AP 00:13:49:c9:b7:76 [11336.730251] wlan0: RX ReassocResp from 00:13:49:c9:b7:76 (capab=0x411 status=0 aid=1) [11336.730251] wlan0: associated [11336.730251] wlan0: switched to short barker preamble (BSSID=00:13:49:c9:b7:76) [18550.507674] wlan0: RX disassociation from 00:13:49:c9:b7:76 (reason=16) [18550.507687] wlan0: disassociated [18551.508711] wlan0: associate with AP 00:13:49:c9:b7:76 [18551.510637] wlan0: RX deauthentication from 00:13:49:c9:b7:76 (reason=6) [18551.510650] wlan0: deauthenticated [18552.510230] wlan0: authenticate with AP 00:13:49:c9:b7:76 [18552.511711] wlan0: RX authentication from 00:13:49:c9:b7:76 (alg=0 transaction=2 status=0) [18552.511724] wlan0: authenticated [18552.511731] wlan0: associate with AP 00:13:49:c9:b7:76 [18552.513767] wlan0: RX ReassocResp from 00:13:49:c9:b7:76 (capab=0x411 status=0
Bug#497971: linux-image-2.6.26-1-686: Workaround found
Package: linux-image-2.6.26-1-686 Version: 2.6.26-4 Followup-For: Bug #497971 Create file /etc/modprobe.d/iwlwifi-fix with following content: options cfg80211 ieee80211_regdom=EU This fixes the problem on my laptop. But obviously this should not be the solution to this problem. Either Debian installer should create such a file, or some other automated solution shall detect IWL WiFi card and create this workaround. Or driver should read proper regdom from the card's EEPROM. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495708: iwlwifi: loss of the connection and subsequent failure to restore it until reboot
Package: linux-image-2.6.25-2-686 Version: 2.6.25-7 Severity: normal Connection to the access point breaks after several reassociations and driver (I suspect) gets into a strange state when it is unable to associate or authenticate again. I use NetworkManager to handle Wi-Fi connections. Noteworthy, that in the very beginning iwlist and NetworkManager list all wireless networks available. But when this situation happens neither NetworkManager nor iwlist tool do not list my wireless network (it is not hidden), though all other wireless networks are listed. It is defenitly not Access Point failure, since other computers continue to use the Wi-Fi successfuly. Some info regarding my WLAN. It is not hidden. It is encrypted with WPA2. According to the log my access point sends disassociation requests every hour and driver does reassociation and reauthentiacation. But after n-th case somewhat happens The relevant portion of syslog follows: Aug 19 08:19:53 wardriver0 kernel: [32230.490556] wlan0: RX disassociation from 00:13:49:c9:b7:76 (reason=16) Aug 19 08:19:53 wardriver0 kernel: [32230.490556] wlan0: disassociated Aug 19 08:19:53 wardriver0 NetworkManager: info Supplicant state changed: 0 Aug 19 08:19:54 wardriver0 kernel: [32231.206930] wlan0: associate with AP 00:13:49:c9:b7:76 Aug 19 08:19:54 wardriver0 kernel: [32231.208527] wlan0: RX deauthentication from 00:13:49:c9:b7:76 (reason=6) Aug 19 08:19:54 wardriver0 kernel: [32231.208537] wlan0: deauthenticated Aug 19 08:19:54 wardriver0 NetworkManager: info Supplicant state changed: 0 Aug 19 08:19:55 wardriver0 kernel: [32231.938431] wlan0: authenticate with AP 00:13:49:c9:b7:76 Aug 19 08:19:55 wardriver0 kernel: [32231.939703] wlan0: RX authentication from 00:13:49:c9:b7:76 (alg=0 transaction=2 status=0) Aug 19 08:19:55 wardriver0 kernel: [32231.939714] wlan0: authenticated Aug 19 08:19:55 wardriver0 kernel: [32231.939721] wlan0: associate with AP 00:13:49:c9:b7:76 Aug 19 08:19:55 wardriver0 kernel: [32231.941572] wlan0: RX ReassocResp from 00:13:49:c9:b7:76 (capab=0x411 status=0 aid=1) Aug 19 08:19:55 wardriver0 kernel: [32231.941582] wlan0: associated Aug 19 08:19:55 wardriver0 kernel: [32231.941592] wlan0: switched to short barker preamble (BSSID=00:13:49:c9:b7:76) Aug 19 08:19:55 wardriver0 kernel: [32231.941641] iwl4965: Error sending REPLY_RXON_ASSOC: Already sending a host command Aug 19 08:19:59 wardriver0 NetworkManager: info Supplicant state changed: 1 Aug 19 08:47:01 wardriver0 -- MARK -- Aug 19 09:07:01 wardriver0 -- MARK -- Aug 19 09:17:01 wardriver0 /USR/SBIN/CRON[32464]: (root) CMD ( cd / run-parts --report /etc/cron.hourly) Aug 19 09:19:58 wardriver0 kernel: [34868.940339] wlan0: RX disassociation from 00:13:49:c9:b7:76 (reason=16) Aug 19 09:19:58 wardriver0 kernel: [34868.940339] wlan0: disassociated Aug 19 09:19:58 wardriver0 NetworkManager: info Supplicant state changed: 0 Aug 19 09:19:59 wardriver0 kernel: [34869.664856] wlan0: associate with AP 00:13:49:c9:b7:76 Aug 19 09:19:59 wardriver0 kernel: [34869.666496] wlan0: RX deauthentication from 00:13:49:c9:b7:76 (reason=6) Aug 19 09:19:59 wardriver0 kernel: [34869.666506] wlan0: deauthenticated Aug 19 09:19:59 wardriver0 NetworkManager: info Supplicant state changed: 0 Aug 19 09:20:00 wardriver0 kernel: [34870.393243] wlan0: authenticate with AP 00:13:49:c9:b7:76 Aug 19 09:20:00 wardriver0 kernel: [34870.394611] wlan0: RX authentication from 00:13:49:c9:b7:76 (alg=0 transaction=2 status=0) Aug 19 09:20:00 wardriver0 kernel: [34870.394623] wlan0: authenticated Aug 19 09:20:00 wardriver0 kernel: [34870.394630] wlan0: associate with AP 00:13:49:c9:b7:76 Aug 19 09:20:00 wardriver0 kernel: [34870.396511] wlan0: RX ReassocResp from 00:13:49:c9:b7:76 (capab=0x411 status=0 aid=1) Aug 19 09:20:00 wardriver0 kernel: [34870.396523] wlan0: associated Aug 19 09:20:00 wardriver0 kernel: [34870.396533] wlan0: switched to short barker preamble (BSSID=00:13:49:c9:b7:76) Aug 19 09:20:00 wardriver0 kernel: [34870.396583] iwl4965: Error sending REPLY_RXON_ASSOC: Already sending a host command Aug 19 09:20:04 wardriver0 NetworkManager: info Supplicant state changed: 1 Aug 19 09:47:01 wardriver0 -- MARK -- Aug 19 10:07:01 wardriver0 -- MARK -- Aug 19 10:17:01 wardriver0 /USR/SBIN/CRON[1810]: (root) CMD ( cd / run-parts --report /etc/cron.hourly) Aug 19 10:20:02 wardriver0 kernel: [37519.464378] wlan0: RX disassociation from 00:13:49:c9:b7:76 (reason=16) Aug 19 10:20:02 wardriver0 kernel: [37519.464378] wlan0: disassociated Aug 19 10:20:02 wardriver0 NetworkManager: info Supplicant state changed: 0 Aug 19 10:20:03 wardriver0 kernel: [37520.183210] wlan0: associate with AP 00:13:49:c9:b7:76 Aug 19 10:20:03 wardriver0 kernel: [37520.184936] wlan0: RX deauthentication from 00:13:49:c9:b7:76 (reason=6) Aug 19 10:20:03 wardriver0 kernel: [37520.184946] wlan0: deauthenticated Aug 19 10:20:03 wardriver0 NetworkManager: info Supplicant state changed: 0 Aug
Bug#495708: Ответ: Bug#495708: iwlwifi: loss of the connection and subsequent failure to restore it until reboot
2008/8/20, maximilian attems [EMAIL PROTECTED]: On Wed, Aug 20, 2008 at 01:01:03AM +0400, Max Dmitrichenko wrote: Package: linux-image-2.6.25-2-686 Version: 2.6.25-7 Severity: normal unsupported kernel, upgrade to latest 2.6.26 has newer iwlwifi. What the heck?! This is the kernel that is currently in lenny. And isn't lenny going to be realesed with this kernel? Moreover, according to packages.debian.org there is no kernel of version 2.6.26 in repository. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493633: linux-source-2.6.25: Suggest libncurses5-dev instead of libncurses-dev
Package: linux-source-2.6.25 Version: 2.6.25-7 Severity: normal There is no package libncurses-dev any more. Please update suggest list. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-source-2.6.25 depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii bzip2 1.0.5-0.1high-quality block-sorting file co Versions of packages linux-source-2.6.25 recommends: ii gcc 4:4.3.1-2 The GNU C compiler ii libc6-dev [libc-dev] 2.7-10 GNU C Library: Development Librari ii make 3.81-5 The GNU version of the make util Versions of packages linux-source-2.6.25 suggests: ii kernel-package11.001-0.1 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.6+20080713-1 developer's libraries and docs for pn libqt3-mt-dev none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#493355: kwin: strange behaviour with apps running in fullscreen mode
Package: kwin Version: 4:3.5.9.dfsg.1-4 Severity: normal I used to use separate desktops for some applications like konsole or emacs. I tune window specific settings to run each of these apps on a separate desktop in a fullscreen mode. Now I've upgraded from etch to lenny and noticed a behaviour change which makes me upset. Following steps should reproduce it: 1) Run konsole and press ctrl-shift-F to switch to fullscreen view. 2) Switch to another desktop. 3) Run another application, e.g. konqueror. 4) Switch back to the desktop where konsole is running. Notice? The kicker is on top of the fullscreen konsole, though the focus is in the konsole window. You can try to explicitly bring focus to the konsole window, but kicker will stay. The only way to get rid of kicker is to click into the konsole window, then switch to any other desktop and switch back again. Such behaviour doesn't depend of the app running in fullscreen mode. Tested with konsole, konqueror and emacs. This is either kwin's bug or kicker's one. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores) Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages kwin depends on: ii kdelibs4c2a 4:3.5.9.dfsg.1-6 core libraries and binaries for al ii libc6 2.7-10 GNU C Library: Shared libraries ii libgcc1 1:4.3.1-2GCC support library ii libice6 2:1.0.4-1X11 Inter-Client Exchange library ii libqt3-mt 3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-2X11 Session Management library ii libstdc++6 4.3.1-2 The GNU Standard C++ Library v3 ii libx11-62:1.1.4-2X11 client-side library ii libxcomposite1 1:0.4.0-3X11 Composite extension library ii libxdamage1 1:1.1.1-4X11 damaged region extension libra ii libxext62:1.0.4-1X11 miscellaneous extension librar ii libxfixes3 1:4.0.3-2X11 miscellaneous 'fixes' extensio ii libxrender1 1:0.9.4-2X Rendering Extension client libra kwin recommends no packages. Versions of packages kwin suggests: ii kdebase-bin 4:3.5.9.dfsg.1-4 core binaries for the KDE base mod ii kdebase-data4:3.5.9.dfsg.1-4 shared data files for the KDE base ii kdesktop4:3.5.9.dfsg.1-4 miscellaneous binaries and files f ii kicker 4:3.5.9.dfsg.1-4 desktop panel for KDE ii kpager 4:3.5.9.dfsg.1-4 desktop pager for KDE ii kpersonalizer 4:3.5.9.dfsg.1-4 installation personalizer for KDE ii ksmserver 4:3.5.9.dfsg.1-4 session manager for KDE ii ksplash 4:3.5.9.dfsg.1-4 the KDE splash screen -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#491967: ksmserver package should have dependence on x11-utils package
Package: ksmserver Version: 4:3.5.9.dfsg.1-2+b1 Severity: important /usr/bin/startkde script calls the xprop util which belongs to x11-utils package. Without it KDE appears to start but has some strange effects, e.g. every second log on happens without kwin running, as a consequence all windows don't have a frame. Also there is only one desktop available in this case. When I was installing lenny, I chose only Standart system in the tasksel and then also installed kde-core and kdm packages. This way I've got a system where x11-utils were not installed. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ksmserver depends on: ii kdelibs4c2a 4:3.5.9.dfsg.1-6core libraries and binaries for al ii kwin [x-window-manag 4:3.5.9.dfsg.1-2+b1 the KDE window manager ii libc62.7-10 GNU C Library: Shared libraries ii libgcc1 1:4.3.1-2 GCC support library ii libice6 2:1.0.4-1 X11 Inter-Client Exchange library ii libqt3-mt3:3.3.8b-5 Qt GUI Library (Threaded runtime v ii libsm6 2:1.0.3-2 X11 Session Management library ii libstdc++6 4.3.1-2 The GNU Standard C++ Library v3 ii libx11-6 2:1.1.4-2 X11 client-side library ii libxau6 1:1.0.3-3 X11 authorisation library Versions of packages ksmserver recommends: ii kpersonalizer4:3.5.9.dfsg.1-2+b1 installation personalizer for KDE -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454263: xserver-xorg-input-vmmouse: Providing Device option helps to solve this issue
Package: xserver-xorg-input-vmmouse Version: 1:12.5.1-2 Followup-For: Bug #454263 Adding: Option Device /dev/input/mice to the InputDevice section lets X start with mouse which visually behaves like a correct working VMWare mouse. I.e. it ungrabs input when cursor leaves virtual machine's region. But good news end here. It seems that virtual machine's X server then thinks that mouse is always in the right bottom corner of virtual machine's screen. E.g. if I have KDE kicker then any click on the mouse left button will hide the kicker (there is hide button) and any click on right button will show kicker's context menu. If another window occupies right bottom area of the screen, then any mouse click have reaction specific to that window. Note, that visual cursor behaves OK - it moves perfectly around the screen. It enters and leaves VMWare and grabs and ungrabs the input correspondingly. It can point to any point on the VMWare screen but there is no feedback for it, e.g. like on-mouse-over events. So, logically it behaves like mouse pointer is always in the right bottom corner. May be this is a side effect of specifying Device option. I'm not sure whether it is right to specify /dev/input/mice for vmmouse driver. But otherwise call to xf86OpenSerial() function fails, because vmmouse driver doesn't fill the Device option. Moreover, there is no other mouse device in system except /dev/input/mice. -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2008-07-23 00:09 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1718228 2008-06-26 04:14 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 00:0f.0 VGA compatible controller: VMware Inc Abstract SVGA II Adapter /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1311 2008-07-23 08:33 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver vmmouse Option Device /dev/input/mice EndSection Section Device Identifier Configured Video Device EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice Configured Mouse CorePointer InputDevice Generic Keyboard CoreKeyboard EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 26136 2008-07-23 08:33 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-1) Current Operating System: Linux lenny 2.6.25-2-686 #1 SMP Fri Jul 18 17:46:56 UTC 2008 i686 Build Date: 26 June 2008 01:58:50AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Wed Jul 23 08:33:26 2008 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device Configured Video Device (**) |--Input Device Configured Mouse (**) |--Input Device Generic Keyboard (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory /usr/share/fonts/X11/cyrillic does not exist. Entry
Bug#386640: wodim: The same bug bothers me
Package: wodim Version: 9:1.1.2-1 Followup-For: Bug #386640 I have the same behavior on my new box. The conditions are completly the same: premastered image, DVD+R medium. I have burned 5 disks with the same error. Disks are usable under Linux, but I failed to read them under Windows. I haven't yet tried DVD-R or any other medium. Why doesn't this bug have any reaction from Wodim maintainers for such a long time? Do you need any additional info? Below is some information about my drive, sorry but burning logs were not saved. Linux sg driver version: 3.5.27 Wodim version: 1.1.2 Driveropts: 'burnfree' SCSI buffer size: 64512 atapi: 1 Device type: Removable CD-ROM Version: 5 Response Format: 2 Capabilities : Vendor_info: 'Optiarc ' Identification : 'DVD RW AD-7173S ' Revision : '1-01' Device seems to be: Generic mmc2 DVD-R/DVD-RW. Current: 0x (Reserved/Unknown) Profile: 0x002B (DVD+R/DL) Profile: 0x001B (DVD+R) Profile: 0x001A (DVD+RW) Profile: 0x0016 (DVD-R/DL layer jump recording) Profile: 0x0015 (DVD-R/DL sequential recording) Profile: 0x0014 (DVD-RW sequential recording) Profile: 0x0013 (DVD-RW restricted overwrite) Profile: 0x0012 (DVD-RAM) Profile: 0x0011 (DVD-R sequential recording) Profile: 0x0010 (DVD-ROM) Profile: 0x000A (CD-RW) Profile: 0x0009 (CD-R) Profile: 0x0008 (CD-ROM) Profile: 0x0002 (Removable disk) Using generic SCSI-3/mmc CD-R/CD-RW driver (mmc_cdr). Driver flags : MMC-3 SWABAUDIO BURNFREE Supported modes: TAO PACKET SAO SAO/R96R RAW/R96R -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22-3-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages wodim depends on: ii libc6 2.3.6.ds1-13etch4 GNU C Library: Shared libraries ii libcap11:1.10-14 support for getting/setting POSIX. Versions of packages wodim recommends: ii genisoimage 9:1.1.2-1 Creates ISO-9660 CD-ROM filesystem -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#459780: emdebian-tools: emsource uses / as working directory by default
Package: emdebian-tools Version: 0.7.3 Severity: normal The man page for the emsource tool says: workingdir: A simple default location for emsource to create a source tree to download, unpack and patch source packages. Leave blank to use a subdirectory of the current directory. But in fact emsource tries to use the root directory to download sources and patches from SVN. -- Package-specific info: -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22-3-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages emdebian-tools depends on: ii apt0.6.46.4-0.1 Advanced front-end for dpkg ii apt-cross 0.7.0~dmitrmax.1 retrieve, build and install librar ii automake 1:1.10+nogfdl-1 A tool for generating GNU Standard ii binutils-multiarch 2.17-3Binary utilities that support mult ii cdbs 0.4.48common build system for Debian pac ii dbs0.42 Allows Debian source packages with ii debconf [debconf-2.0] 1.5.11etch1 Debian configuration management sy ii debhelper 5.0.61~dmitrmax.1 helper programs for debian/rules ii debootstrap1.0.7~dmitrmax.1 Bootstrap a basic Debian system ii devscripts 2.9.26Scripts to make the life of a Debi ii dpatch 2.0.21patch maintenance system for Debia ii dpkg-cross 2.1.1 tools for cross compiling Debian p ii dpkg-dev 1.14.8~dmitrmax.1 package building tools for Debian ii edos-debcheck 1.0-2 Checks whether dependencies of deb ii fakeroot 1.5.10Gives a fake root environment ii g++4:4.1.1-15The GNU C++ compiler ii gcc4:4.1.1-15The GNU C compiler ii gettext0.16.1-1 GNU Internationalization utilities ii libcache-apt-perl 0.7.0~dmitrmax.1 object oriented apt cache perl bin ii libconfig-auto-perl0.18-1Magical config file parser ii libfile-homedir-perl 0.56-1.1 Get the home directory for yoursel ii libparse-debianchangel 1.0-1 parse Debian changelogs and output ii libtext-diff-perl 0.35-2Perform diffs on files and record ii libtext-formattable-pe 1.01-1Format text tables ii libwww-perl5.805-1 WWW client/server library for Perl ii pbuilder 0.161 personal package builder for Debia ii perl 5.8.8-7etch1 Larry Wall's Practical Extraction ii quilt 0.45-6Tool to work with series of patche ii sudo 1.6.8p12-4Provide limited super user privile ii ucf2.0020Update Configuration File: preserv Versions of packages emdebian-tools recommends: ii subversion 1.4.2dfsg1-2 Advanced version control system -- debconf information: emsetup/aptagent: true emsource/svnusername: emsource/targetsuite: unstable emsource/workdir: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#455793: vmware-package: Add debconf dialogs to choose the network addresses of host-only networks vmnet1 and vmnet8
Package: vmware-package Version: 0.20 Severity: normal The network addresses of vmnet1 and vmnet8 are hardcoded to be 192.168.1.0/24 and 192.168.8.0/24 correspondingly. The former is a very often used value so making it default is a very bad. Personaly I sent about an hour to find out why all the computers on my LAN became unpingable. This happend because 192.168.1.0/24 was set on both interfaces: eth0 and vmnet1. I was neither asked whether I agree with this nor warned about this. At least debconf warning message should be shown to the user. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22-3-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages vmware-package depends on: ii bzip2 1.0.3-6 high-quality block-sorting file co ii debhelper 5.0.61~dmitrmax.1 helper programs for debian/rules ii dpkg-dev 1.13.25 package building tools for Debian ii fakeroot 1.5.10Gives a fake root environment ii file 4.17-5etch3 Determines file type using magic ii make 3.81-2The GNU version of the make util ii module-assistant 0.10.8tool to make module package creati ii prelink0.0.20061027-1ELF prelinking utility to speed up ii python 2.4.4-2 An interactive high-level object-o Versions of packages vmware-package recommends: ii ia32-libs 1.19 ia32 shared libraries for use on a pn ia32-libs-gtk none (no description available) ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libatk1.0-0 1.12.4-3 The ATK accessibility toolkit ii libbz2-1.01.0.3-6high-quality block-sorting file co ii libcairo2 1.2.4-4The Cairo 2D vector graphics libra pn libcairomm-1.0-1 none (no description available) pn libcroco3 none (no description available) ii libexpat1 1.95.8-3.4 XML parsing C library - runtime li ii libfontconfig12.4.2-1.2 generic font configuration library ii libfreetype6 2.2.1-5+etch1 FreeType 2 font engine, shared lib pn libglade2-0 none (no description available) ii libglib2.0-0 2.12.4-2 The GLib library of C routines pn libglibmm-2.4-1c2anone (no description available) pn libgnomecanvas2-0 none (no description available) pn libgnomecanvasmm-2.6-1c2a none (no description available) pn libgsf-1-114 none (no description available) ii libgtk2.0-0 2.8.20-7 The GTK+ graphical user interface pn libgtkmm-2.4-1c2a none (no description available) ii libpango1.0-0 1.14.8-5 Layout and rendering of internatio ii libpng12-01.2.15~beta5-1 PNG library - runtime pn librsvg2-2none (no description available) pn libsexy2 none (no description available) pn libsexymm2none (no description available) ii libsigc++-2.0-0c2a2.0.17-2 type-safe Signal Framework for C++ pn libview2 none (no description available) ii libx11-6 2:1.0.3-7 X11 client-side library ii libxau6 1:1.0.1-2 X11 authorisation library ii libxcursor1 1.1.7-4X cursor management library ii libxdmcp6 1:1.0.1-2 X11 Display Manager Control Protoc ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxfixes31:4.0.1-5 X11 miscellaneous 'fixes' extensio ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxi61:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1X11 Xinerama extension library ii libxml2 2.6.27.dfsg-1 GNOME XML library ii libxrandr22:1.1.0.2-5X11 RandR extension library ii libxrender1 1:0.9.1-3 X Rendering Extension client libra ii libxtst6 1:1.0.1-5 X11 Testing -- Resource extension ii zlib1g1:1.2.3-13 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454671: xserver-xorg-input-evdev: Certain keys are not repeated when they are pressed and held down
2007/12/7, Julien Cristau [EMAIL PROTECTED]: Please send your X log and config, and the output of 'setxkbmap -print' or 'xprop -root _XKB_RULES_NAMES' when using evdev. I've solve the problem. When using evdev driver, one should choose XkbModel evdev instead of pc104 and then everything will work. I think this should be explicitly noted in something like README.Debian, because evdev driver will set the proper XkbModel by default, but default Debian's setup of xorg.conf overrides this default to pc104. So I won't close this bug for now, ok? -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#454671: xserver-xorg-input-evdev: Certain keys are not repeated when they are pressed and held down
Package: xserver-xorg-input-evdev Version: 1:1.1.2-6 Severity: normal Following keys are not repeated when they are held down: 1) End 2) Left arrow 3) Down arrow All other keys were checked with xev and they are repeated (except locks and modifiers). Also everything works fine when kbd drivers is used instread of evdev. Not sure, but when I used to use Debian for i386 (as opposed to amd64 for now), it seems to me that this bug didn't occured. May be architecture is also involved. Additional information: I use Microsoft Natural 4000 USB keyboard. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22-3-amd64 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg-input-evdev depends on: ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries ii xserver-xorg-core 2:1.1.1-21etch1 X.Org X server -- core server xserver-xorg-input-evdev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#448363: psi: Configure script should be supplied with --disable-bundled-qca option
Package: psi Version: 0.11-1 Severity: normal Not supplying --disable-bundled-qca option leads Psi to link staticly against the QCA2 version (and its plugins) shipped with Psi source code in third-party directory. This should be avoided. Patch is trivial, so not attached. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-sparc64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages psi depends on: ii libaspell15 0.60.4-4 GNU Aspell spell-checker runtime l ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries ii libgcc1 1:4.1.1-21 GCC support library ii libqt4-core 4.3.1-2Qt 4 core non-GUI functionality ru ii libqt4-gui4.3.1-2Qt 4 core GUI functionality runtim ii libqt4-qt3support 4.3.1-2Qt 3 compatibility library for Qt ii libssl0.9.8 0.9.8c-4etch1 SSL shared libraries ii libstdc++64.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxss1 1:1.1.0-1 X11 Screen Saver extension library ii zlib1g1:1.2.3-13 compression library - runtime Versions of packages psi recommends: ii libqca2-plugin 0.1~20070904-3QCA OSSL plugin for libqca2 pn soxnone(no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445916: psi: More info about this bug
Package: psi Version: 0.11~rc3-1 Followup-For: Bug #445916 Tested on the i386 under the same conditions. Psi does NOT segfault on i386. Moreover, investigation of the sparc's version core dump showed that segfault happens somewhere deep inside Qt4. There is some bug in gdb that prevents me to get full backtrace after I've installed libqt4-debug. But that's what gdb says about zeroth frame: #0 QTextFormat::setObjectIndex (this=0xffeed708, o=0) This function deals with QSharedData and QSharedDataPointer which use architecture specific atomic variables. I suspect that Qt4's implementation of atomics is somehow broken on SPARC. May be this bug should be forwarded to qt4 package, but I haven't figured out any other application which suffers from this bug. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#445916: psi: Segfaults on sparc when choosing the User Info
Package: psi Version: 0.11~rc3-1 Severity: important Steps to reproduce. 1) Create an account 2) Connect to the server 3) Choose any user and click User Info or press Ctrl-I. Additional notes. I'm running Debian Etch and I have backported this package from experimental. It refused to compile on etch because the configure script requires at least Qt 4.2.3 to be install while Etch has Qt 4.2.1. But since there are no differenses in the API between 4.2.1 and 4.2.3, I have manually dropped the requirement to 4.2.1 and then compiled it successfuly. I don't beleive that this can be reason for such a segfault. I haven't tested it yet on i386. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-sparc64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages psi depends on: ii libaspell150.60.4-4 GNU Aspell spell-checker runtime l ii libc6 2.3.6.ds1-13etch2 GNU C Library: Shared libraries ii libgcc11:4.1.1-21GCC support library ii libqt4-core4.2.1-2+etch1 Qt 4 core non-GUI functionality ru ii libqt4-gui 4.2.1-2+etch1 Qt 4 core GUI functionality runtim ii libqt4-qt3support 4.2.1-2+etch1 Qt 3 compatibility library for Qt ii libssl0.9.80.9.8c-4etch1 SSL shared libraries ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxss11:1.1.0-1 X11 Screen Saver extension library ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages psi recommends: pn libqca2-plugin-ossl none (no description available) pn sox none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441346: vmware-package: Support for VMWare Tools
Package: vmware-package Version: 0.14~dmitrmax.1 Severity: wishlist It would be very useful to have a possibility to packetize the VMWare Tools. May be it should be even done when doing make-vmpkg on the VMWare Workstation. You just need to rip the linux.iso from vmware-blobs package and create the vmware-tools and vmware-tools-kernel-source packages. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages vmware-package depends on: ii bzip21.0.3-6 high-quality block-sorting file co ii debhelper5.0.42 helper programs for debian/rules ii dpkg-dev 1.13.25 package building tools for Debian ii fakeroot 1.5.10 Gives a fake root environment ii file 4.17-5etch2 Determines file type using magic ii make 3.81-2 The GNU version of the make util ii module-assistant 0.10.8 tool to make module package creati ii python 2.4.4-2 An interactive high-level object-o Versions of packages vmware-package recommends: pn ia32-libs none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413055: kdelibs4c2a: KDE widget that accepts password behaves wrong when keyboard layout is not US
On Friday 20 July 2007 00:12, Sune Vuorela wrote:
One thing I don't fully understand in your bug report. Is it just a
'cosmetic' issue - or does logging in not work?
What if you use backspace? do one or two stars dissapear ?
Ok. I have found the bug and written the patch. The bug is in KPasswordEdit
widget. The author has chosen to store password in a raw char[] array (maybe,
for security reasons). When the password field was updated, it printed as
many * as the length of this array. Backspace deleted only one char, that
is a half of UTF-8 cyrillic char, so this is definitely a bug.
I've tested it with latin and cyrillic passwords, both works!.
--
Max
diff -Nrua sources/kdelibs-3.5.5a.dfsg.1/kdeui/kpassdlg.cpp kdelibs-3.5.5a.dfsg.1/kdeui/kpassdlg.cpp
--- sources/kdelibs-3.5.5a.dfsg.1/kdeui/kpassdlg.cpp 2006-01-19 20:07:18.0 +0300
+++ kdelibs-3.5.5a.dfsg.1/kdeui/kpassdlg.cpp 2007-08-02 05:43:09.0 +0400
@@ -205,7 +205,12 @@
if (e-state() (ControlButton | AltButton))
e-ignore();
else if (m_Length) {
- m_Password[--m_Length] = '\000';
+QString tmp(QString::fromLocal8Bit(m_Password));
+tmp.truncate(tmp.length() - 1);
+
+const QCString localTxt = tmp.local8Bit();
+qstrncpy(m_Password, localTxt, maxPasswordLength());
+ m_Length = localTxt.length();
showPass();
}
break;
@@ -261,15 +266,15 @@
void KPasswordEdit::showPass()
{
-QString tmp;
+QString tmp(QString::fromLocal8Bit(m_Password));
switch (m_EchoMode) {
case OneStar:
- tmp.fill('*', m_Length);
+ tmp.fill('*');
setText(tmp);
break;
case ThreeStars:
- tmp.fill('*', m_Length*3);
+ tmp.fill('*', tmp.length()*3);
setText(tmp);
break;
case NoEcho: default:
@@ -283,7 +288,7 @@
if (newLength = PassLen) newLength = PassLen - 1; // belt and braces
if (newLength 0) newLength = 0;
int* t = ourMaxLength(this);
-*t = newLength;
+*t = newLength;
while (m_Length newLength) {
m_Password[m_Length] = '\000';
--m_Length;
@@ -625,7 +630,7 @@
const double lengthFactor = d-reasonablePasswordLength / 8.0;
-
+
int pwlength = (int) (pass.length() / lengthFactor);
if (pwlength 5) pwlength = 5;
@@ -646,7 +651,7 @@
if ( pwstrength 0 ) {
pwstrength = 0;
}
-
+
if ( pwstrength 100 ) {
pwstrength = 100;
}
Bug#434806: emacs22 doesn't start in fullscreen mode under KDE
Sven Joachim wrote: Max Dmitrichenko writes: I've configured the KDE's kwin WM to put the window of Emacs on the dedicated desktop and switch it to fullscreen as Emacs starts. You did not specify how you did that, do you use kstart? KDE Control Center-Desktop-Window-Specific Settings. There I've created a rule for Emacs' window. I tried to reproduce this with KDE 3.5.7 and emacs22-gtk under sid, running kstart --desktop 2 --fullscreen emacs22 -Q and that left a small gap between the Emacs window and the bottom of the screen, but certainly less than 1/10 of the screen. Yep! That's another, more faster, way to reproduce it. I really didn't know about this wonderful kstart. What about 1/10 - I didn't measure it with a rule. This gap is about as twice higher as kicker on my display. FWIW, it was no different with emacs21. No, it was different. I've been using such configuration since sarge was in testing, it worked when sarge went stable, and works now in the current etch. Note, however, that Emacs 22 has a --fullscreen option itself: when I ran kstart --desktop 2 emacs22 -Q --fullscreen That's another cool tip! Thanks a lot. I guess I switch to this way of launching emacs. the Emacs window duly occupied the whole screen, so you may want to try this instead of whatever you currently use. Ok. But anyway what is described here is a kind of misbehavior, i.e. bug. What you reported is a good workaround, but I think we shouldn't close this bug report. -- WBR, Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434806: emacs22 doesn't start in fullscreen mode under KDE
Package: emacs22 Version: 22.1+1-1 Severity: normal I've configured the KDE's kwin WM to put the window of Emacs on the dedicated desktop and switch it to fullscreen as Emacs starts. This had been working for ages with emacs21 under both Sarge and Etch. But after I backported emacs22 to Etch this stopped working. Instead of expected behavior, kwin puts the Emacs' window on the dedicated desktop and takes the window border off, but it fails to make window fullscreen - it is as wide as screen, but there is about 1/10 of screen height at the bottom not used by Emacs' window. Interresting fact: toggling the fullscreen mode by hands brings to the desired result. This is reproduced with default config, i.e. without .emacs in the home directory, as well as with my own config. P.S.: Of course, it may be a bug of kwin, but since other applications (including emacs21), which I also put onto the dedicated desktops in fullscreen mode, functions as expected, I tend to think this is a bug of Emacs22. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages emacs22 depends on: ii emacs22-bin-common22.1+1-1 The GNU Emacs editor's shared, arc ii libasound21.0.13-2 ALSA library ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libncurses5 5.5-5 Shared libraries for terminal hand ii libpng12-01.2.15~beta5-1 PNG library - runtime ii libsm61:1.0.1-3 X11 Session Management library ii libtiff4 3.8.2-7Tag Image File Format (TIFF) libra ii libungif4g4.1.4-4shared library for GIF images ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxmu6 1:1.0.2-2 X11 miscellaneous utility library ii libxpm4 1:3.5.5-2 X11 pixmap library ii libxt61:1.0.2-2 X11 toolkit intrinsics library ii xaw3dg1.5+E-14 Xaw3d widget set ii zlib1g1:1.2.3-13 compression library - runtime emacs22 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413055: kdelibs4c2a: KDE widget that accepts password behaves wrong when keyboard layout is not US
В сообщении от 20 Июль 2007 00:12 Sune Vuorela написал(a): On Thursday 01 March 2007, Max Dmitrichenko wrote: Package: kdelibs4c2a Version: 4:3.5.5a.dfsg.1-6 Severity: important Tags: l10n I have configured my keyboard for two layouts us and ru. If I switch keyboard to ru layout and KDE dialog prompting password appears then for every character I type into password field two asteriks appear. To Plain Qt programs do not suffer from this bug. Checked on Psi. I suspect that problem is with UTF-8, i.e. entering a two-byte UTF-8 character displays two *. Hi! One thing I don't fully understand in your bug report. Is it just a 'cosmetic' issue - or does logging in not work? What if you use backspace? do one or two stars dissapear ? No, it isn't just a 'cosmetic' issue. Backspace deletes only one star. I didn't check weather a correct password is entered or not, because I don't have passwords which contain non-latin chars. -- Max
Bug#432695: emacs22: Build dependencies requires at least version 0.42-1 of quilt package
Package: emacs22 Version: 22.1+1-1 Severity: minor Otherwise building Debian package failes because quilt before 0.42 doesn't have header command. That was discovered while backporting to Sarge. Under Etch package is builded successfuly. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages emacs22 depends on: ii emacs22-bin-common22.1+1-1 The GNU Emacs editor's shared, arc ii libasound21.0.13-2 ALSA library ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libncurses5 5.5-5 Shared libraries for terminal hand ii libpng12-01.2.15~beta5-1 PNG library - runtime ii libsm61:1.0.1-3 X11 Session Management library ii libtiff4 3.8.2-7Tag Image File Format (TIFF) libra ii libungif4g4.1.4-4shared library for GIF images ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxmu6 1:1.0.2-2 X11 miscellaneous utility library ii libxpm4 1:3.5.5-2 X11 pixmap library ii libxt61:1.0.2-2 X11 toolkit intrinsics library ii xaw3dg1.5+E-14 Xaw3d widget set ii zlib1g1:1.2.3-13 compression library - runtime emacs22 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#427279: emacs22: Is this gonna happen?
Package: emacs22 Followup-For: Bug #427279 So, it's been more than a week since you promised to upload the 22.1 version on the next week. Come on! The sooner you uploads it, the sooner all bugs will be found and corrected :) We are looking forward to it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424759: Ответ: Bug#424759: linux-image-2.6.18-4-xen-686: Please build both PAE and non-PAE kernels for Xen
One search for xen-hypervisor on the Debian packages gives: xen-hypervisor-3.0.3-1-amd64 xen-hypervisor-3.0.3-1-i386 xen-hypervisor-3.0.3-1-i386-pae This means that there is a non-PAE version already available (read the package description). This means that there's only a non-PAE hypervisor available. But there is no kernel compiled w/o PAE. Reading Fedora HOWTO is a doubtful source of information since Fedora provides only PAE hypervisor, so it is true that running Xen on Fedora requires PAE to be enabled in kernel. But in general this is not true. Steve, IMHO, not providing non-PAE kernel images hits the usability of the Xen overall. In the current state only another Linux can be virtualized with Debian's Xen. But what about other good and open OSes wich are supported by non-PAE Xen? The world is not limited with Linux. Of course, I can try to compile such kernel myself, but what that is not obvious procedure, since linux-source package can't be use OOB to compile Xen image with kernel-package. But hey, what about security updates then? One will have to do the recompilation every time the kernel is updated. -- Max 2007/5/19, Teodor [EMAIL PROTECTED]: On 5/17/07, Steve Langasek [EMAIL PROTECTED] wrote: On Thu, May 17, 2007 at 11:20:26AM +0400, Max Dmitrichenko wrote: Using PAE kernels and hypervisor is required for big virtualizing servers. But non-PAE kernels are also required by developers, students and other people who use Xen on their desktop boxes to do OS research, multiplatform development and so on. Providing only PAE kernel disables the ability to run at least NetBSD and OpenSolaris, may be some other OSes too. Please, build also the non-PAE kernels in the future. IMHO this bug should be wontfixed. We already provide binary kernel images for an excessive number of flavors; it's unrealistic to think that we would be able to provide prepackaged images for all possible use cases, the important thing is to provide images that are usable on all target /hardware/, and if a user needs more specific options afterwards that's why we have linux-tree and linux-source packages. One search for xen-hypervisor on the Debian packages gives: xen-hypervisor-3.0.3-1-amd64 xen-hypervisor-3.0.3-1-i386 xen-hypervisor-3.0.3-1-i386-pae This means that there is a non-PAE version already available (read the package description). Note: using the non-PAE version gives a kernel panic on my system. I've read the Fedora HOWTO on XEN and it states that XEN 3 requires PAE to be enabled!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#424759: linux-image-2.6.18-4-xen-686: Please build both PAE and non-PAE kernels for Xen
Package: linux-image-2.6.18-4-xen-686 Version: 2.6.18.dfsg.1-12etch2 Severity: normal Using PAE kernels and hypervisor is required for big virtualizing servers. But non-PAE kernels are also required by developers, students and other people who use Xen on their desktop boxes to do OS research, multiplatform development and so on. Providing only PAE kernel disables the ability to run at least NetBSD and OpenSolaris, may be some other OSes too. Please, build also the non-PAE kernels in the future. Thanx. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-4-xen-686 depends on: ii initramfs-tools0.85g tools for generating an initramfs ii linux-modules-2.6. 2.6.18.dfsg.1-12etch2 Linux 2.6.18 modules on i686 Versions of packages linux-image-2.6.18-4-xen-686 recommends: ii libc6-xen 2.3.6.ds1-13 GNU C Library: Shared libraries [X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417893: Ответ: Bug#417893: subversion: Add debconf interface to create repository and setup snvserve
2007/4/5, Peter Samuelson [EMAIL PROTECTED]: But I _have_ been planning to set up svnserve in the packaging - just haven't had time to add that. It is the next major item on my subversion packaging todo list. Glad to hear this. I'm looking forward to this feature Many thanks for your work! -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417893: subversion: Add debconf interface to create repository and setup snvserve
Package: subversion Version: 1.4.2dfsg1-2 Severity: wishlist It would be very nice to configure such things as creating the repository and setting up the server (Apache or svnserve) with a debconf interface. Otherwise one needs to manually edit Apache/inetd configs which is a bit nasty. As a prototype for such interface, the cvs package debconf could be taken. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages subversion depends on: ii libapr1 1.2.7-8.2The Apache Portable Runtime Librar ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libsvn1 1.4.2dfsg1-2 Shared libraries used by Subversio subversion recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417962: eciadsl: Problem with kernel 2.6.18. Please apply the synch patch
Package: eciadsl Version: 0.11-3.1 Severity: grave Justification: renders package unusable Switching to kernel version 2.6.18 has made the eciadsl completly unusable for the owners of GlobSpan-based modems. But there is a patch published on the homepage of the package which restores the normal function of the package on the kernels 2.6.18 and later. Please apply this patch to the package. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages eciadsl depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries Versions of packages eciadsl recommends: pn ppp none (no description available) ii udev 0.105-4/dev/ and hotplug management daemo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398904: reportbug: The reason causing this bug was found
Package: reportbug Version: 3.33 Followup-For: Bug #398904 This bug happens when generated bug report information countains non-latin characters. For example, reporting bug for xserver-xorg caused such behavior because debconf information was included. Debconf has generated a Russian name for my display and my videocard and when reportbug tryed to include this, it finished up with this UnicodeDecodeError. I wonder why Python tries to convert this to Unicode from ASCII, while I use the ru_RU.UTF-8 locale. It is obvious that all the Russian characters in my case are already in UTF-8, that is they are two-byte long beginning with 0xd0. And that is why I got following message: UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 604: ordinal not in range(128) I guess now it is no problem for those who knows Python to fix the problem, so I'm going to kill moreinfo tag. -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/dmitrmax/.reportbugrc: reportbug_version 3.31 mode advanced ui text email [EMAIL PROTECTED] smtphost smtp.wplus.net -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages reportbug depends on: ii python2.4.4-2An interactive high-level object-o ii python-central0.5.12 register and build utility for Pyt reportbug recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414271: wodim should detect when the device was mounted
Package: wodim Version: 9:1.1.2-1 Severity: minor When I tried to blank the CD-RW, I've got the following repeating message from wodim: Error trying to open /dev/cdrw1 exclusively (Device or resource busy)... retrying in 1 second. That was because I've mounted CD-RW couple of days ago and forgot to unmount it. But it took me 15 minutes to understand that this wasn't a bug in wodim but a bug of mine :) Considering that such things like KDE+pmount can automatically mount inserted CD-media, it would be very good to detect this and show the user more informative message telling that device must be unmounted first. Otherwise new Linux users would be unable to diagnose the problem and to burn an optical media. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages wodim depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libcap1 1:1.10-14support for getting/setting POSIX. Versions of packages wodim recommends: ii genisoimage 9:1.1.2-1 Creates ISO-9660 CD-ROM filesystem -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414125: eclipse-gcj: Package uninstallable on sparc
In a perfect world all packages this would just work as eclipse would build everywhere. The problem is that the eclipse package is not ported to sparc (and some othere architectures). The eclipse-gcj package is architeture independant and therefore available on all architectures. I downgrade this bug to wishlist as eclipse needs serious work to make everything work on sparc. When you install the eclipse package the installation will still fail because the libswt3.2-gtk-jni package is not available on sparc (yet). I just wanted to say that you probably should remove these eclipse packages from sparc in etch. What are they doing in repository if they are unusable and uninstallable? Waste space on CDs and mirrors? -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#414125: eclipse-gcj: Package uninstallable on sparc
Package: eclipse-gcj Version: 3.2.1-4 Severity: grave Justification: renders package unusable I'm trying to install Eclipse on sparc architecture. That's what I get: # LANG=en_US.UTF-8 apt-get install eclipse-gcj Reading package lists... Done Building dependency tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: eclipse-gcj: Depends: eclipse but it is not installable Depends: eclipse-jdt-gcj but it is not installable Depends: eclipse-pde-gcj but it is not installable Depends: eclipse-platform-gcj but it is not installable Depends: eclipse-rcp-gcj but it is not installable Depends: libswt3.2-gtk-gcj but it is not installable E: Broken packages Indeed, none of its dependencies is available on sparc - only intel and powerpc. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-sparc64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#413055: kdelibs4c2a: KDE widget that accepts password behaves wrong when keyboard layout is not US
Package: kdelibs4c2a Version: 4:3.5.5a.dfsg.1-6 Severity: important Tags: l10n I have configured my keyboard for two layouts us and ru. If I switch keyboard to ru layout and KDE dialog prompting password appears then for every character I type into password field two asteriks appear. To reproduce it, you can run Control Center and in any administration applet click appropriate button to switch into admin mode and when dialog prompting root password appears switch the layout to different language and try to type something. Another way to reproduce it is KDE lock screen: try to enter password there with switched layout. Plain Qt programs do not suffer from this bug. Checked on Psi. I suspect that problem is with UTF-8, i.e. entering a two-byte UTF-8 character displays two *. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages kdelibs4c2a depends on: ii kdelibs- 4:3.5.5a.dfsg.1-6 core shared data for all KDE appli ii libacl1 2.2.41-1Access control list shared library ii libart-2 2.3.17-1Library of functions for 2D graphi ii libarts1 1.5.5-1 aRts sound system core components ii libasoun 1.0.13-1ALSA library ii libaspel 0.60.4-4GNU Aspell spell-checker runtime l ii libattr1 2.4.32-1Extended attribute shared library ii libaudio 1.8-3 The Network Audio System (NAS). (s ii libavahi 0.6.16-2Avahi client library ii libavahi 0.6.16-2Avahi common library ii libavahi 0.6.16-2Avahi Qt3 integration library ii libbz2-1 1.0.3-6 high-quality block-sorting file co ii libc62.3.6.ds1-11GNU C Library: Shared libraries ii libcomer 1.39+1.40-WIP-2006.11.14+dfsg-1 common error description library ii libcupsy 1.2.7-4 Common UNIX Printing System(tm) - ii libfontc 2.4.2-1 generic font configuration library ii libfreet 2.2.1-5 FreeType 2 font engine, shared lib ii libgamin 0.1.8-1 Client library for the gamin file ii libgcc1 1:4.1.1-21 GCC support library ii libgnutl 1.4.4-3 the GNU TLS library - runtime libr ii libice6 1:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjaspe 1.701.0-2 The JasPer JPEG-2000 runtime libra ii libjpeg6 6b-13 The Independent JPEG Group's JPEG ii libkrb53 1.4.4-6 MIT Kerberos runtime libraries ii liblua50 5.0.3-2 Main interpreter library for the L ii libluali 5.0.3-2 Extension library for the Lua 5.0 ii libopene 1.2.2-4.3 runtime files for the OpenEXR imag ii libpcre3 6.7-1 Perl 5 Compatible Regular Expressi ii libpng12 1.2.15~beta5-1 PNG library - runtime ii libqt3-m 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc+ 4.1.1-21The GNU Standard C++ Library v3 ii libtiff4 3.8.2-7 Tag Image File Format (TIFF) libra ii libx11-6 2:1.0.3-5 X11 client-side library ii libxcurs 1.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxiner 1:1.0.1-4.1 X11 Xinerama extension library ii libxml2 2.6.27.dfsg-1 GNOME XML library ii libxrand 2:1.1.0.2-5 X11 RandR extension library ii libxrend 1:0.9.1-3 X Rendering Extension client libra ii libxslt1 1.1.19-1XSLT processing library - runtime ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii menu-xdg 0.2.3 freedesktop.org menu compliant win ii perl 5.8.8-7 Larry Wall's Practical Extraction ii xbase-cl 1:7.1.ds1-2 miscellaneous X clients ii zlib1g 1:1.2.3-13 compression library - runtime Versions of packages kdelibs4c2a recommends: pn perl-suid none (no description available) -- no debconf information
Bug#413056: kdesktop_lock behaves badly with kxkb enabled
Package: kdesktop Version: 4:3.5.5a.dfsg.1-6 Severity: normal 1) Enable kxkb in the Control Center. 2) Choose two keyboard layouts (I reproduce this bug with us and ru). 3) Lock the session. 4) There is a small button for choosing layout in the unlocking dialog under the password field. Click it! 5) You'll see how the password field starts being filled with a lot of *. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing'), (200, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages kdesktop depends on: ii eject 2.1.4-2.1 ejects CDs and operates CD-Changer ii kdebase-bin4:3.5.5a.dfsg.1-6 core binaries for the KDE base mod ii kdelibs4c2a4:3.5.5a.dfsg.1-6 core libraries and binaries for al ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libaudio2 1.8-3 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-21GCC support library ii libgl1-mesa-glx [libgl 6.5.1-0.6 A free implementation of the OpenG ii libglu1-mesa [libglu1] 6.5.1-0.6 The OpenGL utility library (GLU) ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libkonq4 4:3.5.5a.dfsg.1-6 core libraries for Konqueror ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-5 X11 client-side library ii libxau61:1.0.1-2 X11 authorisation library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxss11:1.1.0-1 X11 Screen Saver extension library ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii libxxf86misc1 1:1.0.1-2 X11 XFree86 miscellaneous extensio ii zlib1g 1:1.2.3-13compression library - runtime kdesktop recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409982: xkb-data: Patch fixing this problem was accepted into the upstream at fd.o
Package: xkb-data Version: 0.9-4 Followup-For: Bug #409982 The patch I've sent before was accepted by the maintainer of xkeyboard-config at freedesktop.org into the upstream. So, please apply it in Debian. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-sparc64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412352: xkb-data: Right Meta key sets the wrong modifier in compat/misc
Package: xkb-data
Version: 0.9-4
Severity: normal
Tags: patch
This seems to be an obvious copy-paste bug. Patch attached.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
-- no debconf information
diff -ur xkeyboard-config-0.9/compat/misc xkeyboard-config-0.9.fixed/compat/misc
--- xkeyboard-config-0.9/compat/misc 2005-11-27 02:17:11.0 +0300
+++ xkeyboard-config-0.9.fixed/compat/misc 2007-02-25 18:38:56.0 +0300
@@ -58,7 +58,7 @@
};
interpret Meta_R {
- action = SetMods(modifiers=Alt);
+ action = SetMods(modifiers=Meta);
};
// Sets the Super virtual modifier
Bug#409982: xkb-data: Patch to fix this bug
Package: xkb-data
Version: 0.9-4
Followup-For: Bug #409982
The patch attached renames this invalid keysym to XF86Eject thus fixing the
problem.
May be it is reasonable to send this patch to the upstream of xkeyboard-config
project.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
-- no debconf information
diff -ur xkeyboard-config-0.9/symbols/inet
xkeyboard-config-0.9.fixed/symbols/inet
--- xkeyboard-config-0.9/symbols/inet 2006-09-18 17:51:37.0 +0400
+++ xkeyboard-config-0.9.fixed/symbols/inet 2007-02-25 21:57:47.0
+0300
@@ -2229,7 +2229,7 @@
key I6C { [ XF86Mail] };
key I78 { [ XF86Copy] };
key K65 { [ XF86Paste ] };
-key K6C { [ XF86AudioEject ] };
+key K6C { [ XF86Eject ] };
key K75 { [ XF86ScrollUp] };
key XFER { [ XF86AudioMedia ] };
};
Bug#398904: reportbug: bug was reproduced on version 3.33 too
Package: reportbug Version: 3.33 Followup-For: Bug #398904 The situation is the same in the version 3.33 og reportbug. What more information do you need to fix it? -- Package-specific info: ** /home/dmitrmax/.reportbugrc: reportbug_version 3.31 mode advanced email [EMAIL PROTECTED] smtphost smtp.wplus.net -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-sparc64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages reportbug depends on: ii python2.4.4-2An interactive high-level object-o ii python-central0.5.12 register and build utility for Pyt reportbug recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411962: kdebase-bin: evdev driver somehow involved
Package: kdebase-bin Version: 4:3.5.5a.dfsg.1-6 Followup-For: Bug #411962 I've reproduced this bug on two i386 boxes and one sparc64 box. It appears only when evdev driver is used while kbd works fine. But it is still not obvious how the driver inflicts khotkeys. The only fact I can appeal is that with khotkeys disabled everything just works with evdev. Why I use the evdev driver? It's because it is the only alternative to get use of all the keys on Sun Type 5 keyboard on 2.6 kernels. Furthermore, it is the only way to get multi-head work for several users. So, I would like to get this bug fixed in the release. Thanks in advance. P.S.: I'm trying to look into the source code. I keep you informed if I would find something. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-sparc64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages kdebase-bin depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-6 core libraries and binaries for al ii libacl12.2.41-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libattr1 2.4.32-1 Extended attribute shared library ii libaudio2 1.8-3 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libfam02.7.0-12 Client library to control the FAM ii libfontconfig1 2.4.2-1 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-21GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpam-runtime 0.79-4Runtime support for the PAM librar ii libpam0g 0.79-4Pluggable Authentication Modules l ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-5 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxkbfile11:1.0.3-2 X11 keyboard file manipulation lib ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii libxtst6 1:1.0.1-5 X11 Testing -- Resource extension ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages kdebase-bin recommends: pn gdb none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411827: kcalc: package dependencies problem
Package: kcalc Version: 4:3.5.5-3 Severity: important kcalc depends on libgmp3c2 package but it's not on kcalc's dependency list. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-sparc64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411840: procps: ps doesn't resolve uid-username of some processes
Package: procps Version: 1:3.2.7-3 Severity: normal Processes which are running under users haldaemon and messagebus are displayed somehow different by ps utility. The following output of ps shows that their uids are not resolved into usernames. They are left 102 and 103 correspondingly. A simple test program that uses getpwuid() libc function works correctly, so this is not a bug of libc6 but the bug of procps package. $ ps aux USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.2 2472 632 ?Ss Feb20 0:02 init [2] root 2 0.0 0.0 0 0 ?SN Feb20 0:00 [ksoftirqd/0] root 3 0.0 0.0 0 0 ?S Feb20 0:01 [events/0] root 4 0.0 0.0 0 0 ?S Feb20 0:00 [khelper] root 5 0.0 0.0 0 0 ?S Feb20 0:00 [kthread] root73 0.0 0.0 0 0 ?SFeb20 0:00 [powerd] root74 0.0 0.0 0 0 ?S Feb20 0:00 [kblockd/0] root77 0.0 0.0 0 0 ?S Feb20 0:00 [khubd] root79 0.0 0.0 0 0 ?S Feb20 0:00 [kseriod] root 118 0.0 0.0 0 0 ?SFeb20 0:00 [pdflush] root 119 0.0 0.0 0 0 ?SFeb20 0:03 [pdflush] root 120 0.0 0.0 0 0 ?S Feb20 0:01 [kswapd0] root 121 0.0 0.0 0 0 ?S Feb20 0:00 [aio/0] root 752 0.0 0.0 0 0 ?S Feb20 0:00 [kpsmoused] root 1933 0.0 0.0 0 0 ?S Feb20 0:00 [kjournald] root 2094 0.0 0.1 2984 448 ?Ss Feb20 0:01 udevd --daemon root 3102 0.0 0.0 0 0 ?S Feb20 0:00 [kmirrord] root 3134 0.0 0.0 0 0 ?S Feb20 0:01 [kjournald] root 3136 0.0 0.0 0 0 ?S Feb20 0:00 [kjournald] root 3523 0.0 0.2 1992 720 ?Ss Feb20 0:00 /sbin/syslogd root 3529 0.0 0.1 1872 416 ?Ss Feb20 0:00 /sbin/klogd -x 102 3536 0.0 0.2 3152 560 ?Ss Feb20 0:00 /usr/bin/dbus-daemon --system 103 3544 0.0 0.3 11888 960 ?Ss Feb20 0:02 /usr/sbin/hald root 3545 0.0 0.2 4104 552 ?SFeb20 0:00 hald-runner 103 3557 0.0 0.2 2728 744 ?SFeb20 0:00 hald-addon-keyboard: listening on /dev/input/event0 root 3561 0.0 0.2 2232 616 ?SFeb20 0:00 hald-addon-storage: polling /dev/hdc -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages procps depends on: ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libncurses5 5.5-5Shared libraries for terminal hand ii lsb-base3.1-23 Linux Standard Base 3.1 init scrip Versions of packages procps recommends: ii psmisc22.3-1 Utilities that use the proc filesy -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398904: reportbug: the same problem occurs when reporting bug for xserver-xorg
Package: reportbug Version: 3.31 Followup-For: Bug #398904 While trying to sumbit bug for xserver-xorg, I get the following: -CUT HERE- Please briefly describe your problem (you can elaborate in a moment; an empty response will stop reportbug). This should be a concise summary of what is wrong with the package, for example, fails to send email or does not start with -q option specified. package dependencies problem Rewriting subject to 'xserver-xorg: package dependencies problem' Enter any additional addresses this report should be sent to; press ENTER after each address. Press ENTER on a blank line to continue. How would you rate the severity of this problem or report? 1 criticalmakes unrelated software on the system (or the whole system) break, or causes serious data loss, or introduces a security hole on systems where you install the package. 2 grave makes the package in question unusable by most or all users, or causes data loss, or introduces a security hole allowing access to the accounts of users who use the package. 3 serious is a severe violation of Debian policy (that is, the problem is a violation of a 'must' or 'required' directive); may or may not affect the usability of the package. Note that non-severe policy violations may be 'normal,' 'minor,' or 'wishlist' bugs. (Package maintainers may also designate other bugs as 'serious' and thus release-critical; however, end users should not do so.) 4 important a bug which has a major effect on the usability of a package, without rendering it completely unusable to everyone. 5 does-not-build a bug that stops the package from being built from source. (This is a 'virtual severity'.) 6 normal a bug that does not undermine the usability of the whole package; for example, a problem with a particular option or menu item. 7 minor things like spelling mistakes and other minor cosmetic errors that do not affect the core functionality of the package. 8 wishlistsuggestions and requests for new features. Please select a severity level: [normal] Do any of the following apply to this report? 1 l10n This bug reports a localization/internationalization issue. 2 patch You are including a patch to fix this problem. 3 none Please select tags: (one at a time) [none] Traceback (most recent call last): File /usr/bin/reportbug, line 1747, in ? main() File /usr/bin/reportbug, line 779, in main return iface.user_interface() File /usr/bin/reportbug, line 1645, in user_interface klass, subject, tags, body, mode, pseudos) File /usr/share/reportbug/reportbug.py, line 729, in generate_blank_report return %s%s%s UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 604: ordinal not in range(128) -CUT HERE- -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/dmitrmax/.reportbugrc: reportbug_version 3.31 mode advanced ui text email [EMAIL PROTECTED] smtphost smtp.wplus.net -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages reportbug depends on: ii python2.4.4-2An interactive high-level object-o ii python-central0.5.12 register and build utility for Pyt Versions of packages reportbug recommends: pn python-cjkcodecs | python-ico none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411962: kdebase-bin: khotkeys mixes up the Up key and Print key
Package: kdebase-bin Version: 4:3.5.5a.dfsg.1-6 Severity: important I've installed KDE and after my first login I've discovered the Up key doesn't work properly while Left, Right and Down keys work normal. If I press Up key then KSnapShot launches. When I opened KHotKey settings, there was only one enabled keyboard action and it was configured on Print key to launch ksnapshot. But Print key doesn't do its function. Instead Up key works. So when I disabled this action, Up key started to work right. I have to sad that I have done no configuration either of KDE or of its parts, that means that situation must be reproducible on the default setup. And I can reproduce it by creating a new user a logining for the first time into KDE session. xev recognizes keys correctly - I've checked. So, definitely it is a bug of khotkeys or one of its part or library. May be it will be also useful FYI - XKB is configured with evdev driver. This is configuration of my keyboard: Section InputDevice Identifier Generic Keyboard Driver evdev Option CoreKeyboard Option evBits +1 Option keyBits ~1-255 ~352-511 Option Pass3 Option XkbRules xorg Option XkbModel evdev Option XkbLayout us,ru Option XkbOptionsaltwin:meta_win EndSection -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-sparc64 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Versions of packages kdebase-bin depends on: ii kdelibs4c2a4:3.5.5a.dfsg.1-6 core libraries and binaries for al ii libacl12.2.41-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libattr1 2.4.32-1 Extended attribute shared library ii libaudio2 1.8-3 The Network Audio System (NAS). (s ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libfam02.7.0-12 Client library to control the FAM ii libfontconfig1 2.4.2-1 generic font configuration library ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-21GCC support library ii libice61:1.0.1-2 X11 Inter-Client Exchange library ii libidn11 0.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpam-runtime 0.79-4Runtime support for the PAM librar ii libpam0g 0.79-4Pluggable Authentication Modules l ii libpng12-0 1.2.15~beta5-1PNG library - runtime ii libqt3-mt 3:3.3.7-3 Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3 X11 Session Management library ii libstdc++6 4.1.1-21 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-5 X11 client-side library ii libxcursor11.1.7-4 X cursor management library ii libxext6 1:1.0.1-2 X11 miscellaneous extension librar ii libxft22.1.8.2-8 FreeType-based font drawing librar ii libxi6 1:1.0.1-4 X11 Input extension library ii libxinerama1 1:1.0.1-4.1 X11 Xinerama extension library ii libxkbfile11:1.0.3-2 X11 keyboard file manipulation lib ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender11:0.9.1-3 X Rendering Extension client libra ii libxt6 1:1.0.2-2 X11 toolkit intrinsics library ii libxtst6 1:1.0.1-5 X11 Testing -- Resource extension ii zlib1g 1:1.2.3-13compression library - runtime Versions of packages kdebase-bin recommends: pn gdb none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386795: cdimage.debian.org: Update CDs for 3.1r3 contain DEBs which 3.1r3 DVDs don't contain
Package: cdimage.debian.org Severity: normal -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.16-argentum Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) I've updated my DVDs using jigdo to 3.1r3. Then I decided to make update CDs using jigdo and told it to scan my DVDs for the files. After both DVDs were scanned for files form update CD-1 of 3.1r3, jigdo tells me that 22 files were missing and will be downloaded. I've allways thought that file set must be identical on DVDs and CDs. So I report the bug. The list of missing files followed: pool/contrib/a/asm/libasm-java_1.5.2-1_all.deb pool/contrib/a/azureus/azureus_2.2.0.2-1_i386.deb pool/contrib/b/batik/libbatik-java_1.5.1-1_all.deb pool/contrib/b/bluez-utils/bluez-bcm203x_2.15-1.1_i386.deb pool/contrib/b/btools/libbtools-java_1.1-5_all.deb pool/contrib/g/groovy/groovy_0.1.0beta10-2_all.deb pool/contrib/f/fop/fop_0.20.5-5_all.deb pool/contrib/f/freeguide/freeguide_0.8.5-1_all.deb pool/contrib/f/freemind/freemind_0.7.1-6_all.deb pool/contrib/j/jikes-contrib/jikes-sun_0.8_all.deb pool/contrib/libi/libitext-java/libitext-java_1.02b-4_all.deb pool/contrib/libj/libjazzy-java/libjazzy-java_0.5-3_all.deb pool/contrib/libj/libjcommon-java/libjcommon-java_0.8.3-4_all.deb pool/contrib/libj/libjfreechart-java/libjfreechart-java_0.9.8-3_all.deb pool/contrib/libj/libjfreereport-java/libjfreereport-java_0.8.3c-5_all.deb pool/contrib/libp/libpixie-java/libpixie-java_20030705-4_all.deb pool/contrib/libs/libsapdbc7.5.01-java/libsapdbc7.5.01-java_7.5.01.00-2_all.deb pool/contrib/libt/libtoolbar-java/libtoolbar-java_0.2-2_all.deb pool/contrib/libt/libtoolbutton-java/libtoolbutton-java_0.2-2_all.deb pool/contrib/m/mplayerplug-in/mozilla-mplayer_2.70-1_i386.deb pool/contrib/r/rhdb-explain/rhdb-explain_2.0-1_all.deb pool/contrib/x/xmmplayer/xmms-xmmplayer_0.3.3-1_i386.deb May be second and third update CDs also contain some DEB which are missing on DVDs. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384323: Bug#384248: installation-report: Almost successful Etch installation with di-beta3
it is mentioned in the installer. But then /etc/console/boottime.keymap.gz and /etc/console-tools/config should be configured properly with a certain tool. I am not experienced with the details of how the installer works, so Indeed, they are. Localechooser's finish-install does so but, from Eugenyi explanations, it indeed overwrites the defaults set by the console-cyrillic package itself. Indeed, I see two ways to go: -remove console-cyrillic for Russian and do just like we do for Ukrainian AFAIK, console-cyrillic is just a set of cyrillic fonts, keymaps and a script to tie them up. One thing to mention is that keymap is generated dynamically by the script from a base keymap and a chosen method of layout switching. That's all. I've always wondered about why not to include all these fonts into console-data or kbd package (not sure what is currently used in Etch)? The same can be done with keymaps. The feature for choosing a method for the layout switching is very useful though, IMHO. So, may be it is reasonable to support such a feature on the D-I level for all languages which have non-latin keyboard layout without a dedicated key for layout switching? That way we can get rid of console-cyrillic and make the keyboard layout managment more generic and language independent. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384740: installation-report: Some remarks on Russian support in d-i beta3
User/password setup offers to create an ordinary user account. An attemp to enter the real name in Russian in text mode installer failed: instead of russian letters the text field is filled with sequences like C3D8D5. This happens because the loaded Russian keyboard layout (located in file /usr/share/keymaps/i386/qwerty/ru.kmap.gz on the initrd image) uses KOI8-R encoding. And I have chosen the ru_RU.UTF-8 locale when installer prompted. Obvious solution is to replace current keymap with UTF-8 one like it is done for Ukrainian language. But that way another problem arise: what to do with other locales (ru_RU.KOI8-R, ru_RU.CP-1251 and ru_RU) because they won't have usable russian layout. Does anybody know why all other Russian keymaps (for various encodings) from console-data package are symlinks to the ru.kmap.gz on the installer initrd image? -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384323: Bug#384248: installation-report: Almost successful Etch installation with di-beta3
it is mentioned in the installer. But then /etc/console/boottime.keymap.gz and /etc/console-tools/config should be configured properly with a certain tool. I am not experienced with the details of how the installer works, so Indeed, they are. Localechooser's finish-install does so but, from Eugenyi explanations, it indeed overwrites the defaults set by the console-cyrillic package itself. Indeed, I see two ways to go: -remove console-cyrillic for Russian and do just like we do for Ukrainian AFAIK, console-cyrillic is just a set of cyrillic fonts, keymaps and a script to tie them up. One thing to mention is that keymap is generated dynamically by the script from a base keymap and a chosen method of layout switching. That's all. I've always wondered about why not to include all these fonts into console-data or kbd package (not sure what is currently used in Etch)? The same can be done with keymaps. The feature for choosing a method for the layout switching is very useful though, IMHO. So, may be it is reasonable to support such a feature on the D-I level for all languages which have non-latin keyboard layout without a dedicated key for layout switching? That way we can get rid of console-cyrillic and make the keyboard layout managment more generic and language independent. -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#338576: console-data: Updated ru.po file as requested by Christian Perrier [EMAIL PROTECTED]
Package: console-data Version: 2002.12.04dbs-49 Severity: wishlist Tags: l10n patch Five fuzzy messages are removed and properly translated. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.12-dmitrmax Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R) Versions of packages console-data depends on: ii console-common0.7.49 Basic infrastructure for text cons ii debconf 1.4.30.13 Debian configuration management sy -- debconf information: console-data/keymap/qwertz/german/standard/keymap: console-data/keymap/qwertz/swiss/german/keymap: console-data/keymap/qwertz/german/apple_usb/keymap: console-data/keymap/qwerty/estonian/standard/keymap: console-data/keymap/qwerty/swedish/variant: console-data/keymap/qwertz/serbian/standard/keymap: console-data/keymap/qwertz/serbian/variant: console-data/keymap/template/layout: * console-data/keymap/qwerty/layout: Russian console-data/keymap/azerty/layout: console-data/keymap/azerty/french/variant: console-data/keymap/qwerty/lithuanian/standard/keymap: console-data/keymap/qwerty/finnish/variant: console-data/keymap/qwertz/czech/variant: console-data/keymap/qwerty/portugese/standard/keymap: console-data/keymap/fggiod/turkish/standard/keymap: * console-data/keymap/qwerty/russian/standard/keymap: KOI8-R (MS Cyrillic Layout) console-data/keymap/qwerty/swedish/apple_usb/keymap: * console-data/keymap/family: qwerty console-data/keymap/qwerty/brazilian/br-latin1/keymap: console-data/keymap/qwerty/estonian/variant: console-data/keymap/qwertz/swiss/french/keymap: console-data/keymap/dvorak/layout: console-data/keymap/qwerty/romanian/standard/keymap: console-data/keymap/qwerty/finnish/apple_usb/keymap: console-data/keymap/qwertz/swiss/variant: console-data/keymap/qwerty/norwegian/variant: console-data/keymap/qwerty/slovak/variant: console-data/keymap/qwerty/canadian/french/keymap: console-data/keymap/qwerty/hungarian/variant: console-data/keymap/qwertz/german/variant: console-data/keymap/qwerty/macedonian/variant: console-data/keymap/azerty/belgian/apple_usb/keymap: console-data/keymap/qwerty/brazilian/standard/keymap: console-data/keymap/qwertz/slovene/standard/keymap: console-data/keymap/qwerty/british/variant: console-data/keymap/qwerty/ukrainian/variant: console-data/keymap/azerty/french/with_euro__latin_9_/keymap: console-data/keymap/qwerty/icelandic/standard/keymap: console-data/keymap/qwerty/british/apple_usb/keymap: console-data/keymap/qwertz/slovak/variant: console-data/keymap/qwerty/bulgarian/standard/keymap: console-data/keymap/qwerty/czech/standard/keymap: console-data/keymap/qwerty/latvian/standard/keymap: console-data/keymap/qwerty/latin_american/variant: console-data/keymap/qwerty/spanish/apple_usb/keymap: console-data/keymap/dvorak/unknown/right_single-handed/keymap: console-data/keymap/qwerty/us_american/apple_usb/keymap: console-data/keymap/powerpcadb: console-data/keymap/qwerty/serbian/variant: console-data/keymap/azerty/belgian/standard/keymap: console-data/keymap/qwertz/croat/variant: console-data/keymap/qwertz/czech/standard/keymap: console-data/keymap/qwerty/canadian/english/keymap: console-data/keymap/fggiod/turkish/variant: console-data/keymap/template/variant: console-data/keymap/qwerty/romanian/variant: console-data/keymap/qwerty/greek/variant: console-data/keymap/qwerty/bulgarian/variant: console-data/keymap/dvorak/unknown/standard/keymap: console-data/keymap/qwerty/polish/variant: console-data/keymap/dvorak/unknown/left_single-handed/keymap: console-data/keymap/qwerty/turkish/variant: console-data/keymap/ignored: console-data/keymap/qwerty/icelandic/variant: console-data/keymap/azerty/belgian/wang/keymap: console-data/keymap/qwerty/danish/variant: console-data/keymap/qwerty/finnish/standard/keymap: console-data/keymap/qwerty/bulgarian/cp_1251_coding/keymap: console-data/keymap/qwerty/latvian/variant: console-data/keymap/dvorak/unknown/variant: console-data/keymap/qwerty/hebrew/variant: console-data/keymap/qwerty/lithuanian/variant: console-data/keymap/qwerty/hebrew/standard/keymap: console-data/keymap/qwertz/hungarian/standard/keymap: console-data/keymap/fggiod/layout: console-data/keymap/qwerty/norwegian/standard/keymap: console-data/keymap/qwertz/slovak/standard/keymap: console-data/keymap/qwerty/british/standard/keymap: console-data/keymap/qwerty/us_american/standard/keymap: console-data/keymap/qwertz/hungarian/variant: console-data/keymap/qwerty/czech/variant: console-data/keymap/qwerty/hungarian/standard/keymap: console-data/keymap/qwerty/polish/standard/keymap: console-data/keymap/qwerty/ukrainian/standard/keymap: console-data/keymap/qwerty/canadian/variant: console-data/keymap/dvorak/unknown/apple_usb/keymap: console-data/keymap/qwerty/spanish/variant: console-data/keymap/full:
Bug#301712: ttf-freefont: Cannot choose FreeMono font to be monospaced font in KDE
Package: ttf-freefont Version: 20031008-1.1 Severity: normal I don´t find FreeMono font when I try to select the monospaced font in the KDE Conrol Center or, for example, in Konsole. It seems like it is treated not as a monospaced font but propotional, because it presents in the other dialog boxes for selecting fonts. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8 Locale: LANG=ru_RU, LC_CTYPE=ru_RU (charmap=KOI8-R) Versions of packages ttf-freefont depends on: ii defoma0.11.8-0.1 Debian Font Manager -- automatic f -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
