Bug#1068378: [PATCH] Add the pam_keyinit session module to create new sessionkeyring on login
This commit replicates commits[1][2] from the openssh package. Closes [1] https://salsa.debian.org/ssh-team/openssh/-/commit/ca7f6f719ad5f168b25165caaff658f21c784c4e [2] https://salsa.debian.org/ssh-team/openssh/-/commit/dc461e571bcc56f8d95e83c731007636d8e79da5 Closes: #1068378 --- debian/rules | 10 +- debian/xdm.pam| 19 --- debian/xdm.pam.in | 20 3 files changed, 29 insertions(+), 20 deletions(-) delete mode 100644 debian/xdm.pam create mode 100644 debian/xdm.pam.in diff --git a/debian/rules b/debian/rules index 5d2dbd3..ab9f5d4 100755 --- a/debian/rules +++ b/debian/rules @@ -38,6 +38,7 @@ ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) endif DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH) +DEB_HOST_ARCH_OS ?= $(shell dpkg-architecture -qDEB_HOST_ARCH_OS) DEB_HOST_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_HOST_GNU_TYPE) DEB_BUILD_ARCH_OS ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS) DEB_BUILD_GNU_TYPE ?= $(shell dpkg-architecture -qDEB_BUILD_GNU_TYPE) @@ -58,6 +59,13 @@ endif BUILD_DIR := build +debian/xdm.pam: debian/xdm.pam.in +ifeq ($(DEB_HOST_ARCH_OS),linux) + sed 's/^@IF_KEYINIT@//' $< > $@ +else + sed '/^@IF_KEYINIT@/d' $< > $@ +endif + stampdir_targets+=config config: $(STAMP_DIR)/config $(STAMP_DIR)/config: $(STAMP_DIR)/patch @@ -121,7 +129,7 @@ clean: xsfclean dh_clean # Build architecture-dependent files here. -binary-arch: $(STAMP_DIR)/install +binary-arch: $(STAMP_DIR)/install debian/xdm.pam dh_testdir dh_testroot diff --git a/debian/xdm.pam b/debian/xdm.pam deleted file mode 100644 index 1108a71..000 --- a/debian/xdm.pam +++ /dev/null @@ -1,19 +0,0 @@ -auth requisite pam_nologin.so -auth requiredpam_env.so -auth requiredpam_env.so envfile=/etc/default/locale - -# SELinux needs to be the first session rule. This ensures that any -# lingering context has been cleared. Without this it is possible -# that a module could execute code in the wrong domain. -session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close -session requiredpam_loginuid.so -# SELinux needs to intervene at login time to ensure that the process -# starts in the proper default security context. Only sessions which are -# intended to run in the user's context should be run after this. -session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open -sessionrequiredpam_limits.so - -@include common-auth -@include common-account -@include common-session -@include common-password diff --git a/debian/xdm.pam.in b/debian/xdm.pam.in new file mode 100644 index 000..92c46b7 --- /dev/null +++ b/debian/xdm.pam.in @@ -0,0 +1,20 @@ +auth requisite pam_nologin.so +auth requiredpam_env.so +auth requiredpam_env.so envfile=/etc/default/locale + +# SELinux needs to be the first session rule. This ensures that any +# lingering context has been cleared. Without this it is possible +# that a module could execute code in the wrong domain. +session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close +session requiredpam_loginuid.so +@IF_KEYINIT@session optionalpam_keyinit.so force revoke +# SELinux needs to intervene at login time to ensure that the process +# starts in the proper default security context. Only sessions which are +# intended to run in the user's context should be run after this. +session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open +sessionrequiredpam_limits.so + +@include common-auth +@include common-account +@include common-session +@include common-password -- 2.39.2
Bug#1068378: xdm: pam_keyinit is missing from /etc/pam.d/xdm
Package: xdm Version: 1:1.1.11-3+b2 Severity: normal X-Debbugs-Cc: none, Łukasz Stelmach Dear Maintainer, pam_keyinit is missing from the /etc/pam.d/xdm configuration file. Therefore, it is not possible to access the session keyring from programs running in a session started by xdm. The patch will follow. PS. Below there is a modifide pam file from my system which makes it possible to access the session keyring. -- System Information: Debian Release: 12.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: arm64, armel Kernel: Linux 6.5.0-0.deb12.4-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.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 xdm depends on: ii cpp4:12.2.0-3 ii debconf [debconf-2.0] 1.5.82 ii libc6 2.36-9+deb12u4 ii libcrypt1 1:4.4.33-2 ii libpam0g 1.5.2-6+deb12u1 ii libselinux13.4-1+b6 ii libx11-6 2:1.8.4-2+deb12u2 ii libxau61:1.0.9-1 ii libxaw72:1.0.14-1 ii libxdmcp6 1:1.1.2-3 ii libxext6 2:1.3.4-1+b1 ii libxft22.3.6-1 ii libxinerama1 2:1.1.4-3 ii libxmu62:1.1.3-3 ii libxpm41:3.5.12-1.1+deb12u1 ii libxrender11:0.9.10-1.1 ii libxt6 1:1.2.1-1.1 ii lsb-base 11.6 ii procps 2:4.0.2-3 ii sysvinit-utils [lsb-base] 3.06-4 ii x11-utils 7.7+5 ii x11-xserver-utils 7.7+9+b1 xdm recommends no packages. xdm suggests no packages. -- Configuration Files: /etc/pam.d/xdm changed: authrequisite pam_nologin.so authrequiredpam_env.so authrequiredpam_env.so envfile=/etc/default/locale session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close session requiredpam_loginuid.so session optionalpam_keyinit.so force revoke session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open session requiredpam_limits.so @include common-auth @include common-account @include common-session @include common-password -- debconf information: * shared/default-x-display-manager: xdm xdm/daemon_name: /usr/bin/xdm xdm/stop_running_server_with_children: false -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#1023609: smbclient does not work with Kerberos ccache of KEYRING: type
Control: tag -1 patch
Control: forwarded -1 https://gitlab.com/samba-team/samba/-/merge_requests/3021
Hi,
My investigation has reveald that the built in version of Heimdall is
perfectly(?) capable of supporting KEYRING ccache. However it needs to
be properly configured. The configuration code is there in
autoconf/automake files of Heimdal but is missing from samba wscript*
files.
I am attaching a patch I've made against debian/2%4.17.7+dfsg-1_bpo11+1.
With this patch applied and LD_LIBRARY_PATH set to
LD_LIBRARY_PATH=${HOME}/src/debian/samba/samba/debian/tmp/usr/lib/x86_64-linux-gnu/samba
smbclient from the original debian package (2:4.17.7+dfsg-1~bpo11+1) is
capable of using KEYRING ccache. The patch applies cleanly to master too
(e437c9288a3c as of now).
--
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics
From d76344ee0cefcf8adb42928537ba031dd585f797 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C5=81ukasz=20Stelmach?=
Date: Mon, 3 Apr 2023 10:07:30 +0200
Subject: [PATCH] Configure builtin heimdal to support KEYRING ccache
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Organization: Samsung R Institute Poland
Signed-off-by: Åukasz Stelmach
---
third_party/heimdal_build/wscript_build | 8 ++--
third_party/heimdal_build/wscript_configure | 2 ++
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/third_party/heimdal_build/wscript_build b/third_party/heimdal_build/wscript_build
index 1518afe9ef4..8aea52b55f5 100644
--- a/third_party/heimdal_build/wscript_build
+++ b/third_party/heimdal_build/wscript_build
@@ -710,7 +710,7 @@ if not bld.CONFIG_SET("USING_SYSTEM_KRB5"):
get_port.c init_creds.c init_creds_pw.c
kcm.c keyblock.c keytab.c keytab_any.c
keytab_file.c keytab_memory.c
- keytab_keyfile.c krbhst.c log.c
+ keytab_keyfile.c krbhst.c krcache.c log.c
mcache.c misc.c mk_error.c mk_priv.c
mk_rep.c mk_req.c mk_req_ext.c
mit_glue.c net_read.c net_write.c n-fold.c padata.c pkinit.c pkinit-ec.c
@@ -726,10 +726,14 @@ if not bld.CONFIG_SET("USING_SYSTEM_KRB5"):
mk_cred.c kx509_err.c
k524_err.c krb_err.c k5e1_err.c''')] + ["../heimdal_build/krb5-glue.c"]
+krb5_keyutils_dep = ''
+if bld.CONFIG_SET('HAVE_KEYCTL_GET_PERSISTENT'):
+krb5_keyutils_dep = ' keyutils'
+
HEIMDAL_LIBRARY('krb5', KRB5_SOURCE,
version_script='lib/krb5/version-script.map',
includes='../heimdal/lib/krb5 ../heimdal/lib/asn1 ../heimdal/include',
-deps='roken wind asn1 hx509 HEIMDAL_KX509_ASN1 hcrypto com_err HEIMDAL_CONFIG heimbase execinfo samba_intl HEIMDAL_IPC_CLIENT KRB5_CRYPTO',
+deps='roken wind asn1 hx509 HEIMDAL_KX509_ASN1 hcrypto com_err HEIMDAL_CONFIG heimbase execinfo samba_intl HEIMDAL_IPC_CLIENT KRB5_CRYPTO' + krb5_keyutils_dep,
cflags=['-DLOCALSTATEDIR="/2"'] + bld.dynconfig_cflags(),
)
KRB5_PROTO_SOURCE = KRB5_SOURCE + ['lib/krb5/expand_path.c', 'lib/krb5/plugin.c', 'lib/krb5/context.c', 'lib/krb5/crypto.c']
diff --git a/third_party/heimdal_build/wscript_configure b/third_party/heimdal_build/wscript_configure
index a97a1b9baa8..36ba02d25ad 100644
--- a/third_party/heimdal_build/wscript_configure
+++ b/third_party/heimdal_build/wscript_configure
@@ -65,6 +65,8 @@ conf.DEFINE('HAVE_KRB5',1)
conf.CHECK_FUNCS('dirfd', headers='dirent.h')
conf.CHECK_DECLS('dirfd', reverse=True, headers='dirent.h')
conf.CHECK_STRUCTURE_MEMBER('DIR', 'dd_fd', define='HAVE_DIR_DD_FD', headers='dirent.h')
+conf.CHECK_FUNCS_IN('add_key keyctl_get_persistent', 'keyutils', headers='keyutils.h')
+conf.CHECK_SIZEOF('key_serial_t', headers='keyutils.h')
heimdal_no_error_flags = ['-Wno-error=discarded-qualifiers',
'-Wno-error=cast-qual',
--
2.30.2
signature.asc
Description: PGP signature
Bug#1033588: Info received (Bug#1033588: (bash-completion: unquoted tilde in _quote_readline_by_ref causes NSS lookups))
Control: tags -1 +patch
Bug#1033588: (bash-completion: unquoted tilde in _quote_readline_by_ref causes NSS lookups)
Control: -1 +patch
Bug#1028907: cryptsetup: initramfs hook can't handle xchacha20,aes-adantium-plain64
Package: cryptsetup Version: 2:2.3.7-1+deb11u1 Severity: normal X-Debbugs-Cc: Łukasz Stelmach Dear Maintainer, The populate_CRYPTO_MODULES() function in /usr/share/initramfs-tools/hooks/cryptroot can't properly derive required module names (MODULES=dep in initramfs.conf) from dmsetup ouptput when using adantium[1] encryption. In such cases the cipher string is: xchacha20,aes-adantium-plain64 (or xchacha12 on even less performant platforms). Workaround: manually add the following modules to /etc/initramfs-tools/modules: aes_generic chacha_generic nhpoly1350 xts [1] https://lwn.net/Articles/776721/ -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cryptsetup depends on: ii cryptsetup-bin 2:2.3.7-1+deb11u1 ii debconf [debconf-2.0] 1.5.77 ii dmsetup2:1.02.175-2.1 ii libc6 2.31-13+deb11u5 Versions of packages cryptsetup recommends: ii cryptsetup-initramfs 2:2.3.7-1+deb11u1 ii cryptsetup-run2:2.3.7-1+deb11u1 Versions of packages cryptsetup suggests: ii dosfstools 4.2-1 ii keyutils1.6.1-2 ii liblocale-gettext-perl 1.07-4+b1 -- debconf information: cryptsetup/prerm_active_mappings: true -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#1027299: closed by Guilhem Moulin
Guilhem Moulin writes: > On Fri, 30 Dec 2022 at 13:19:10 +0100, Łukasz Stelmach wrote: >> Yes there are workarounds and I've found them, and I won't stay with >> buster longer than necessary, but I am reporting a serious IMHO >> regression. > > While of course not being able to boot is an unfortunate regression, > its scope is very limited True (see my story below). > I'm not arguing it's not a bug, just that there is not much we can do in > oldstable right now. Should one report a security vulnerability in > Buster's src:cryptsetup I'll remember to cherry-pick that change though. BTW. Do you think it may make sense to raise an issue of inadequate policy regarding "premature" sealing of Release Notes? How could I do it? I mean, I think there should be a section for Known Issuse And How To Work Around Them, that stays open for situations like this. Or a wiki page, what's important, is that it exists for every release and is linked from the RN. >> 1. I upgraded to from stretch to buster with linux-image-4.19.0-23-686-pae. >> 2. I rebooted — successfully. >> 2. I installed linux-image-5.10-686-pae from buster/updates (see above). >> 3. 5.10 didn't boot. > > Is there any reason why you don't let the dependency resolver chose > the kernel for you? (`apt install linux-image-686-pae` instead of > specific ABIs.) You would have ended up with 4.9 after dist-upgrading > to stretch, 4.19 after dist-upgrading to buster, and with 5.10 after > dist-upgrading to bullseye. Yes, dist-upgrade to bsuter has left me with 4.19 and it was fine. At this point (before upgrading to bullseye), however, I wanted to upgrade my SSD, because: a) 4 GB (root) + 16 GB (/home) is somewhat little for doing upgrades (yes, I've bind-mounted /home/apt as /var/cache/apt), b) I'd like to encrypt the new SSD with xchacha12,aes-adiantum[1] (27 MB/s vs aes-xts 17 MB/s) which is available since Linux 5.0. Hence, I chose to install 5.10 ASAP. I know, it's a complicated and exceptional story. Let's hope this report will help those few unfortunate who may follow my path. [1] https://lore.kernel.org/linux-crypto/20181117012631.23528-1-ebigg...@kernel.org/ -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#1027299: closed by Guilhem Moulin
Guilhem Moulin writes: > On Fri, 30 Dec 2022 at 00:30:32 +0100, Łukasz Stelmach wrote: >> The version of cryptsetup-initramfs in buster is affected by >> #959423[1]. Although it works with the default 4.19 kernel[2] it fails with >> 5.10 which is available from the main suite and NOT from >> buster-backports. > > No, buster, buster-security, buster-backports respectively have linux > 4.19.249-2, 4.19.269-1, and 5.10.127-2~bpo10+1. Debian doesn't support > a mix and match between oldstable and stable, so if you install the > kernel from stable you need to install cryptsetup-initramfs from > stable as well. > The 5.10 kernel is from oldstable. --8<---cut here---start->8--- $ lsb_release -a Distributor ID: Debian Description:Debian GNU/Linux 10 (buster) Release:10 Codename: buster $ apt policy linux-image-5.10-686-pae linux-image-5.10-686-pae: Installed: 5.10.158-2~deb10u1 Candidate: 5.10.158-2~deb10u1 Version table: *** 5.10.158-2~deb10u1 500 500 tor://security.debian.org buster/updates/main i386 Packages 100 /var/lib/dpkg/status $ apt-cache show linux-image-5.10-686-pae | grep Depends: Depends: linux-image-5.10.0-0.deb10.20-686-pae (= 5.10.158-2~deb10u1) $ apt policy linux-image-5.10.0-0.deb10.20-686-pae linux-image-5.10.0-0.deb10.20-686-pae: Installed: 5.10.158-2~deb10u1 Candidate: 5.10.158-2~deb10u1 Version table: *** 5.10.158-2~deb10u1 500 500 tor://security.debian.org buster/updates/main i386 Packages 100 /var/lib/dpkg/status --8<---cut here---end--->8--- > OTOH mixing buster and buster-backports *is* supported (that's the > reason why backport exist in the first place), so this bug is valid. > But unfortunately buster had its final point release last summer and > IMHO the fix #959423 doesn't qualify for an upload to buster-security, > so I'm closing this. I am not familiar with Debian policies but I belive this is a regression (see below) that deserves a fix. Do reconsider. Or at least a note in the Release Notes, which I followed. >> IMHO the version of cryptsetup-initramfs in buster or buster-updates >> should support 5.10 kernels. > > It does with the default MODULES=dep, and arguably does too in most > situations (these days most systems do support AES-NI, Bad luck, I am upgrading an old Eee PC 901. > and this has been the case since the default LUKS cipher mode was > changed to XTS during the jessie release cycle). In other situations, > workarounds include rebuilding the initramfs with MODULES=most, or > after adding ‘ecb’ to /etc/initramfs-tools/modules, or installing > cryptsetup-initramfs from buster-backports. Yes there are workarounds and I've found them, and I won't stay with buster longer than necessary, but I am reporting a serious IMHO regression. 1. I upgraded to from stretch to buster with linux-image-4.19.0-23-686-pae. 2. I rebooted — successfully. 2. I installed linux-image-5.10-686-pae from buster/updates (see above). 3. 5.10 didn't boot. >> I am upgrading from jessie to bullseye and need 5.10 kernel before the >> last upgrade. > > Upgrades are only supported from n to n+1. A supported upgrade path > would be to dist-upgrade to stretch first and reboot (into the stretch > kernel 4.9), then to buster and reboot (into the buster kernel 4.19) > before finally dist-upgrading to bullseye. Following that upgrade path > you shouldn't stumble onto #959423. I didn't write it explicitly, but I am actually doing n+1. And I #959423 hit me when I tried to boot buster with 5.10 from updates (see above). -- Kind regards, Łukasz Stelmach signature.asc Description: PGP signature
Bug#1027299: cryptsetup: on buster with linux-image-5.10-686-pae aes-xts-plain is not available
Package: cryptsetup-initramfs Version: 2:2.1.0-5+deb10u2 Severity: important X-Debbugs-Cc: none, Łukasz Stelmach Dear Maintainer, The version of cryptsetup-initramfs in buster is affected by #959423[1]. Although it works with the default 4.19 kernel[2] it fails with 5.10 which is available from the main suite and NOT from buster-backports. Installing cryptsetup-initramfs from buster-backports helps. IMHO the version of cryptsetup-initramfs in buster or buster-updates should support 5.10 kernels. I am upgrading from jessie to bullseye and need 5.10 kernel before the last upgrade. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959423 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959423#10 -- Miłego dnia, Łukasz Stelmach
Bug#1009190: Updated version
Hi, I've built the new version locally on. How can I share update debian sources? -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#997010: pius: -e option is broken
Package: pius
Version: 3.0.0-2
Severity: important
Control: tags -1 fixed-upstream
X-Debbugs-Cc: none, Łukasz Stelmach
Dear Maintainer,
Upstream issue report[1] follows:
--8<---cut here---start->8---
I tried
./pius -e -A -r ~/.gnupg/pubring.kbx -s 123456
Got
Traceback (most recent call last):
File "/home/x/pius/./pius", line 365, in
main()
File "/home/x/pius/./pius", line 346, in main
if signer.sign_all_uids(key, retval):
File "/home/x/pius/libpius/signer.py", line 741, in sign_all_uids
self.encrypt_signed_uid(key, uid["file"])
File "/home/x/pius/libpius/signer.py", line 405, in encrypt_signed_uid
gpg.stdin.write("\n")
TypeError: a bytes-like object is required, not 'str'
Everything goes well without -e.
--8<---cut here---end--->8---
The issue has been fixed[2]
[1] https://github.com/jaymzh/pius/issues/138
[2] https://github.com/jaymzh/pius/pull/139
-- System Information:
Debian Release: 11.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU threads)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages pius depends on:
ii gnupg2.2.27-2
ii python3 3.9.2-3
pius recommends no packages.
pius suggests no packages.
-- no debconf information
--
Miłego dnia,
Łukasz Stelmach
Bug#994844: emacs-gtk: Emacs ignores ~/.Xdefaults-HOSTNAME
Package: emacs-gtk
Version: 1:27.1+1-3.1
Severity: normal
Control: tags -1 fixed-upstream
X-Debbugs-Cc: none, Łukasz Stelmach
Dear Maintainer,
After upgrade to Debian 11 Emacs uses default foreground (black) and
background (white) colors instead of those I set in
~/.Xdefaults-myhostname.
strace(8) reveals an attempt to access to a non-existent file
27026 openat(AT_FDCWD, "/home/steelman/.Xdefaults/myhostname", O_RDONLY) =
-1 ENOTDIR[*]
This problem appears (I havn't tested the pathc) to have been
reported[1] and fixed[2] upstream.
The workaround to make Emacs read the file is to set XENVIRONMENT
variable.
XENVIRONMENT=${HOME}/.Xdefaults-myhostname
[*] I've got ~/.Xdefaults file and a bunch of symlinks
to it from ~/.Xdefaults-*
[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=38495
[2]
https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=4b118bdca1d8aa130fb67eadb16e08e87e698aa4
-- System Information:
Debian Release: 11.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU threads)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages emacs-gtk depends on:
ii emacs-bin-common 1:27.1+1-3.1
ii emacs-common 1:27.1+1-3.1
ii libacl1 2.2.53-10
ii libasound2 1.2.4-1.1
ii libc62.31-13
ii libcairo21.16.0-5
ii libdbus-1-3 1.12.20-2
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.10.4+dfsg-1
ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1
ii libgif7 5.1.9-2
ii libglib2.0-0 2.66.8-1
ii libgmp10 2:6.2.1+dfsg-1
ii libgnutls30 3.7.1-5
ii libgpm2 1.20.7-8
ii libgtk-3-0 3.24.24-4
ii libharfbuzz0b2.7.4-1
ii libice6 2:1.0.10-1
ii libjansson4 2.13.1-1.1
ii libjpeg62-turbo 1:2.0.6-4
ii liblcms2-2 2.12~rc1-2
ii libm17n-01.8.0-2
ii libotf0 0.9.13-7
ii libpango-1.0-0 1.46.2-3
ii libpng16-16 1.6.37-3
ii librsvg2-2 2.50.3+dfsg-1
ii libselinux1 3.1-3
ii libsm6 2:1.2.3-1
ii libsystemd0 247.3-6
ii libtiff5 4.2.0-1
ii libtinfo66.2+20201114-2
ii libx11-6 2:1.7.2-1
ii libxext6 2:1.3.3-1.1
ii libxfixes3 1:5.0.3-2
ii libxml2 2.9.10+dfsg-6.7
ii libxrender1 1:0.9.10-1
ii zlib1g 1:1.2.11.dfsg-2
emacs-gtk recommends no packages.
Versions of packages emacs-gtk suggests:
ii emacs-common-non-dfsg 1:27.1+1-2
-- no debconf information
--
Miłego dnia,
Łukasz Stelmach
signature.asc
Description: PGP signature
Bug#994842: elpa-debian-el: (debian-bug) doesn't work after upgrade to Debain 11
Package: elpa-debian-el Version: 37.10 Severity: serious X-Debbugs-Cc: none, Łukasz Stelmach File: /usr/share/emacs/site-lisp/elpa-src/debian-el-37/debian-bug.el Dear Maintainer, After upgrading to Debian 11 I tried to file a bug using M-x debian-bug in Emacs. I didn't get properly prefilled report. Quick investitagion reveald that running reportbug in (debian-bug-prefill-report) failed. (call-process) returned 1 and the lisp code didn't handle it properly. Running the command in a shell yeilded the following message --8<---cut here---start->8--- Warning: no reportbug configuration found. Proceeding in novice mode. Detected character set: UTF-8 Please change your locale if this is incorrect. Unable to identify a valid from address, please run 'reportbug --configure' --8<---cut here---end--->8--- Indeed I didn't have ~/.reportbugrc but until upgrade to Debian 11 it didn't matter and (debian-bug) worked just fine. Configuring reportbug by running "reportbug --configure" as advised fixes the problem. -- System Information: Debian Release: 11.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU threads) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages elpa-debian-el depends on: ii bzip2 1.0.8-4 ii dh-elpa-helper 2.0.8 ii dpkg1.20.9 ii emacsen-common 3.0.4 ii reportbug 7.10.3 ii xz-utils5.2.5-2 Versions of packages elpa-debian-el recommends: ii emacs-gtk [emacs] 1:27.1+1-3.1 ii wget 1.21-1+b1 elpa-debian-el suggests no packages. -- no debconf information -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#991686: gnuplot: invalid utf8 input via terminal
Package: gnuplot Version: 5.2.6+dfsg1-1+deb10u1 Severity: normal Dear Maintainer, 1. Start gnuplot under xterm. 2. Type or paste the command: print "zażółć gęślą jaźń" 3. Gnuplot improperly displays the command typed as: print "zażóÅÄ gÄÅlÄ jaźÅ" The string printed by the command is also invalid. 4. Gnuplot should display edited command and print the string as presented in point 2. Possible fix: Don't use BSD readline library which doesn't support UTF-8 as explained in the help message of gnuplot's configure script: --with-readline=bsd use the NetBSD editline library (NB: does not handle UTF-8!) -- System Information: Debian Release: 10.10 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-17-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gnuplot depends on: ii gnuplot-qt [gnuplot-x11] 5.2.6+dfsg1-1+deb10u1 gnuplot recommends no packages. Versions of packages gnuplot suggests: ii gnuplot-doc 5.2.6+dfsg1-1+deb10u1 -- no debconf information -- Miłego dnia, Łukasz Stelmach
Bug#978450: fixed upstream
Control: fixed -1 0.19~pre1+git20201123.8d73c8f0+dfsg1-1 The bug has been fixed somewhere between upstream commits 3fcbf71fb5 (last failing) and 435815ccc8 (first working). Alas, the commits between are large and don't build and I was unable to spot the exact fix. -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#978450: forwarded
Control: forwarded -1 https://forum.freecadweb.org/viewtopic.php?t=56149 The problem appears to be fixed in upstream 0.19 AppImage releases. -- Miłego dnia, Łukasz Stelmach
Bug#978450: freecad: SEGV when editing a spreadsheet
The problem occurs with freecad-python3 too. -- Miłego dnia, Łukasz Stelmach
Bug#980368: geeqie: Lossless JPEG rotation does not work
Package: geeqie Version: 1:1.4+git20190121-2 Severity: normal Dear Maintainer, I want to losslessly rotate a JPEG file. The file is displayed properly. I choose Edit -> Orientation -> Losslessly rotate JPEG image clockwise. An error dialog appears saying External command failed Can't find matching file type. Unable to start external command. The image orientation does not change as expected. -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages geeqie depends on: ii geeqie-common1:1.4+git20190121-2 ii libatk1.0-0 2.30.0-2 ii libc62.28-10 ii libcairo21.16.0-4 ii libexiv2-14 0.25-4+deb10u1 ii libfontconfig1 2.13.1-2 ii libfreetype6 2.9.1-3+deb10u2 ii libgcc1 1:8.3.0-6 ii libgdk-pixbuf2.0-0 2.38.1+dfsg-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk2.0-0 2.24.32-3 ii libjpeg62-turbo 1:1.5.2-2+deb10u1 ii liblcms2-2 2.9-3 ii liblirc-client0 0.10.1-6.2~deb10u1 ii liblua5.1-0 5.1.5-8.1+b2 ii libpango-1.0-0 1.42.4-8~deb10u1 ii libpangocairo-1.0-0 1.42.4-8~deb10u1 ii libpangoft2-1.0-01.42.4-8~deb10u1 ii libstdc++6 8.3.0-6 ii libtiff5 4.1.0+git191117-2~deb10u1 ii sensible-utils 0.0.12 Versions of packages geeqie recommends: pn cups-bsd | lpr ii exiftran 2.10-3 pn exiv2 ii imagemagick 8:6.9.10.23+dfsg-2.1+deb10u1 ii imagemagick-6.q16 [imagemagick] 8:6.9.10.23+dfsg-2.1+deb10u1 ii librsvg2-common 2.44.10-2.1 pn ufraw-batch pn zenity Versions of packages geeqie suggests: pn geeqie-dbg ii gimp 2.10.8-2 ii libjpeg-turbo-progs [libjpeg-progs] 1:1.5.2-2+deb10u1 pn ufraw pn xpaint -- no debconf information -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#895903: [torsocks] AAAA replies from Tor not handled
On Tue, 17 Apr 2018 13:55:43 +0100 Kevin Steen wrote: > > Tor now returns IPv6 addresses when hostnames are resolved, but > torsocks cannot handle this case. > > To reproduce: > torsocks -d nc ipv6.test-ipv6.com 80 > Without torsocks nc(1) can't perform this request too. $ nc ipv6.test-ipv6.com 80 ipv6.test-ipv6.com: forward host lookup failed: Unknown host $ host ipv6.test-ipv6.com ipv6.test-ipv6.com has IPv6 address 2001:470:1:18::115 This is because nc appears to be using gethostbyname() 1609896026 DEBUG torsocks[27929]: [gethostbyname] Requesting ipv6.test-ipv6.com hostname (in tsocks_gethostbyname() at gethostbyname.c:68) which can't handle records. There is getaddrinfo(3) which is implemented in torsocks. Unfortunately AF_INET6 appears not to be supported yet. If you look at tsocks_tor_resolve() in src/lib/torsocks.c, you will find a stub [1]. [1] https://github.com/dgoulet/torsocks/blob/d4b0a84bdf2a1895c8ec3091dc2767fd9f8c2d66/src/lib/torsocks.c#L527 -- Kind regards, Łukasz Stelmach signature.asc Description: PGP signature
Bug#979384: torsocks: accept() and listen() don't work for AF_INET6 even on localhost
Package: torsocks Version: 2.3.0-2 Severity: normal Control: forwarded -1 https://github.com/dgoulet/torsocks/pull/38 Control: tags -1 + patch Dear Maintainer, I was trying to forward a local TCP to a remote machine over a torified ssh connection but I received the following messages listen: Operation not permitted listen [::1]:6331: Operation not permitted There is a problem in the libtorsocks implementation of listen(), accept() and accept4() functions. They use struct sockaddr to store results of getsockname(2), but the structure is too small for IPv6 addresses and utils_sockaddr_is_localhost() is never true for AF_INET6 sockets. -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages torsocks depends on: ii libc6 2.28-10 Versions of packages torsocks recommends: ii tor 0.3.5.12-1 torsocks suggests no packages. -- no debconf information -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#978458: Acknowledgement (freecad: Addon Manager doesn't fetch list of available addons properly)
Control: tags -1 + fixed-upstream https://github.com/FreeCAD/FreeCAD/commit/258f9f15 is enough to make the Addon Manager work. The other patch provides more robust solution, but contains a typo and requires one more fix tagged 0.18.5. -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#978458: freecad: Addon Manager doesn't fetch list of available addons properly
Package: freecad Version: 0.18~pre1+dfsg1-5 Severity: normal Control: tags -1 + patch Dear Maintainer, Due to updated HTML on github, Addon Manager cannot parse the list of addons properly. This was discussed on the forum[1] and has been fixed in 0.18.5 (commits 258f9f15[2] and b7ab01e6[3]). [1] https://forum.freecadweb.org/viewtopic.php?f=13=51346 [2] https://github.com/FreeCAD/FreeCAD/commit/258f9f15 [3] https://github.com/FreeCAD/FreeCAD/commit/b7ab01e6 -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freecad depends on: ii freecad-python2 0.18~pre1+dfsg1-5 Versions of packages freecad recommends: pn calculix-ccx pn graphviz Versions of packages freecad suggests: pn freecad-doc ii povray 1:3.7.0.8-1 ii python-collada 0.4-3 -- no debconf information -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#978450: freecad: SEGV when editing a spreadsheet
Package: freecad Version: 0.18~pre1+dfsg1-5 Severity: normal Dear Maintainer, From time to time(!), when I press [Tab] or [Enter] to finish editing a cell in a spreadsheet, FreeCAD receives SEGV. I am attaching three stack dumps provided by FreeCAD. -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-13-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freecad depends on: ii freecad-python2 0.18~pre1+dfsg1-5 Versions of packages freecad recommends: pn calculix-ccx pn graphviz Versions of packages freecad suggests: pn freecad-doc ii povray 1:3.7.0.8-1 ii python-collada 0.4-3 -- no debconf information -- Miłego dnia, Łukasz Stelmach App::Document::recompute(): cyclic dependency detected Program received signal SIGSEGV, Segmentation fault. #0 /lib/x86_64-linux-gnu/libc.so.6(+0x37840) [0x7f8f41043840] #1 0x7f8f444b0bfe in std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::find(Base::Type const&) const from /usr/lib/freecad-python2/lib/libFreeCADApp.so+0x5e #2 0x7f8f444afcc3 in App::ExtensionContainer::hasExtension(Base::Type, bool) const from /usr/lib/freecad-python2/lib/libFreeCADApp.so+0x33 #3 0x7f8f444f09e8 in App::GeoFeatureGroupExtension::getGroupOfObject(App::DocumentObject const*) from /usr/lib/freecad-python2/lib/libFreeCADApp.so+0xd8 #4 0x7f8f44bace8e in Gui::DocumentItem::slotChangeObject(Gui::ViewProviderDocumentObject const&) from /usr/lib/freecad-python2/lib/libFreeCADGui.so+0x16e #5 0x7f8f44a70476 in boost::signals2::detail::signal_impl, int, std::less, boost::function, boost::function, boost::signals2::mutex>::operator()(Gui::ViewProviderDocumentObject const&, App::Property const&) from /usr/lib/freecad-python2/lib/libFreeCADGui.so+0x2a6 #6 0x7f8f44a6107f in Gui::Document::slotChangedObject(App::DocumentObject const&, App::Property const&) from /usr/lib/freecad-python2/lib/libFreeCADGui.so+0xaf #7 0x7f8f444988de in boost::signals2::detail::signal_impl, int, std::less, boost::function, boost::function, boost::signals2::mutex>::operator()(App::DocumentObject const&, App::Property const&) from /usr/lib/freecad-python2/lib/libFreeCADApp.so+0x28e #8 0x7f8f444aa291 in App::DocumentObject::onChanged(App::Property const*) from /usr/lib/freecad-python2/lib/libFreeCADApp.so+0x21 #9 0x7f8f4451c605 in App::Property::touch() from /usr/lib/freecad-python2/lib/libFreeCADApp.so+0x35 #10 0x7f8edfecf498 in Spreadsheet::Cell::setContent(char const*) from /usr/lib/freecad-python2/lib/Spreadsheet.so+0xb8 #11 0x7f8edfef023f in Spreadsheet::Sheet::setCell(App::CellAddress, char const*) from /usr/lib/freecad-python2/lib/Spreadsheet.so+0x2f #12 0x7f8edff02b55 in Spreadsheet::SheetPy::set(_object*) from /usr/lib/freecad-python2/lib/Spreadsheet.so+0x165 #13 0x7f8edff02c57 in Spreadsheet::SheetPy::staticCallback_set(_object*, _object*) from /usr/lib/freecad-python2/lib/Spreadsheet.so+0x37 #14 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x7fd0) [0x7f8f43f07f80] #15 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x732) [0x7f8f43eff852] #16 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyEval_EvalCode+0x19) [0x7f8f43effe69] #17 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyRun_StringFlags+0x76) [0x7f8f43ed8286] #18 0x7f8f4422cf06 in Base::InterpreterSingleton::runString[abi:cxx11](char const*) from /usr/lib/freecad-python2/lib/libFreeCADBase.so+0x66 #19 0x7f8f44ab6183 in Gui::Command::doCommand(Gui::Command::DoCmd_Type, char const*, ...) from /usr/lib/freecad-python2/lib/libFreeCADGui.so+0x133 #20 0x7f8edfba27b8 in SpreadsheetGui::SheetModel::setData(QModelIndex const&, QVariant const&, int) from /usr/lib/freecad-python2/lib/SpreadsheetGui.so+0x228 #21 0x7f8edfb929a7 in SpreadsheetGui::SheetView::editingFinished() from /usr/lib/freecad-python2/lib/SpreadsheetGui.so+0xa7 #22 0x7f8f41b2e7f6 in QMetaObject::activate(QObject*, int, int, void**) from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5+0x766 #23 0x7f8edfb8fc3e in SpreadsheetGui::LineEdit::event(QEvent*) from /usr/lib/freecad-python2/lib/SpreadsheetGui.so+0x11e #24 0x7f8f424894c1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x81 #25 0x7f8f42491911 in QApplication::notify(QObject*, QEvent*) from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5+0x11b1 #26 0x7f8f44a8bfd8 in Gui::GUIApplication::notify(QObject*, QEvent*) from /usr/lib/freecad-python2/lib/libFreeCADGui.so+0x88 #27 0x7f8f41b05489 in QCoreApplication::notifyInternal2(QObject*, QEvent*) from /usr/lib/x86_64-linux-g
Bug#976088: freecad: Start Page does not appear after editing a file with non-ascii characters in their name
Package: freecad Version: 0.18~pre1+dfsg1-5 Severity: normal Forwarded: https://github.com/FreeCAD/FreeCAD/pull/4092 Dear Maintainer, When the list of recently edited files contains a file with a non-ascii character in its name. The Start Page fails to show up and the error message appears in the status bar and on the controlling terminal: 'ascii' codec can't decode byte 0xc5 in position 8: ordinal not in range(128) There is a pull request upstream that fixes the issue. -- System Information: Debian Release: 10.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-11-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freecad depends on: ii freecad-python2 0.18~pre1+dfsg1-5 Versions of packages freecad recommends: pn calculix-ccx pn graphviz Versions of packages freecad suggests: pn freecad-doc ii povray 1:3.7.0.8-1 ii python-collada 0.4-3 -- no debconf information -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#966413: freecad: Draft Mirror and other draft tools do not work due to misuse of unicode strings
Package: freecad Version: 0.18~pre1+dfsg1-5 Severity: normal Dear Maintainer, Steps to reproduce: 1. Run freecad from a console (xterm) to see error messages with the following locale settings --8<---cut here---start->8--- LANG=pl_PL.UTF-8 LANGUAGE= LC_CTYPE="pl_PL.UTF-8" LC_NUMERIC="pl_PL.UTF-8" LC_TIME="pl_PL.UTF-8" LC_COLLATE="pl_PL.UTF-8" LC_MONETARY="pl_PL.UTF-8" LC_MESSAGES="pl_PL.UTF-8" LC_PAPER="pl_PL.UTF-8" LC_NAME="pl_PL.UTF-8" LC_ADDRESS="pl_PL.UTF-8" LC_TELEPHONE="pl_PL.UTF-8" LC_MEASUREMENT="pl_PL.UTF-8" LC_IDENTIFICATION="pl_PL.UTF-8" LC_ALL= --8<---cut here---end--->8--- 2. Select Draf workbench 3. Draw an arc. 4. Select the arc. 5. Select Draft Mirror tool. Actual result: The following error message appears on the console idicating problems with a translated string containg unicode encoded Polish diacritic character. --8<---cut here---start->8--- Running the Python command 'Draft_Mirror' failed: Traceback (most recent call last): File "/usr/share/freecad/Mod/Draft/DraftTools.py", line 5204, in Activated self.proceed() File "/usr/share/freecad/Mod/Draft/DraftTools.py", line 5209, in proceed self.ui.pointUi(self.name) File "/usr/share/freecad/Mod/Draft/DraftGui.py", line 998, in pointUi self.showCommandOptions(title) File "/usr/share/freecad/Mod/Draft/DraftGui.py", line 1230, in showCommandOptions cmdstr += v[0] + ":" + v[1] 'ascii' codec can't decode byte 0xc4 in position 5: ordinal not in range(128) --8<---cut here---end--->8--- The tool does not work, the arc isn't mirrored. Side effect: After the exception it is impossible to quit freecad with the exit command in the file menu and closing the window results in a segmentation fault --8<---cut here---start->8--- Program received signal SIGSEGV, Segmentation fault. #0 /lib/x86_64-linux-gnu/libc.so.6(+0x37840) [0x7f7b9c8eb840] #1 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0xd39a4) [0x7f7b9f9679a4] #2 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0x17e5a6) [0x7f7b9fa125a6] #3 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(+0xdf183) [0x7f7b9f973183] #4 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyGC_Collect+0x3c) [0x7f7b9f9676cc] #5 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(Py_Finalize+0xef) [0x7f7b9f97d4ef] #6 0x7f7b9fccfdf2 in Base::InterpreterSingleton::finalize() from /usr/lib/freecad-python2/lib/libFreeCADBase.so+0x12 #7 0x7f7ba0004f04 in App::Application::destruct() from /usr/lib/freecad-python2/lib/libFreeCADApp.so+0x1b4 #8 /usr/bin/freecad(main+0x75a) [0x55a01cc3088a] #9 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f7b9c8d809b] #10 /usr/bin/freecad(_start+0x2a) [0x55a01cc30afa] --8<---cut here---end--->8--- Expected result: No error message, Draft Mirror tool works. Workaround: Run freecad with LC_ALL=C to disable Polish translation. Comment -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages freecad depends on: ii freecad-python2 0.18~pre1+dfsg1-5 Versions of packages freecad recommends: pn calculix-ccx pn graphviz Versions of packages freecad suggests: pn freecad-doc ii povray 1:3.7.0.8-1 ii python-collada 0.4-3 -- no debconf information -- Miłego dnia, Łukasz Stelmach signature.asc Description: PGP signature
Bug#962300: dmraid: dmraid fails do install in a debootstrapped chroot
Source: dmraid Severity: grave Dear Maintainer, On an amd64 host I created armel chroot with qemu-debootstrap. I attempted to install dracut which pulled dmraid and other packages. After installing all packages but dmraid apt install shows following messages (with set -x added to dmraid.postinst) --8<---cut here---start->8--- # LANG=C apt install dracut Reading package lists... Done Building dependency tree Reading state information... Done dracut is already the newest version (048+80-2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up dmraid (1.0.0.rc16-8) ... + command -v update-initramfs + udevadm trigger --subsystem-match=block --action=change Failed to scan devices: No such file or directory dpkg: error processing package dmraid (--configure): installed dmraid package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dmraid E: Sub-process /usr/bin/dpkg returned an error code (1) --8<---cut here---end--->8--- I'd expect the package to install regardles of available devices. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel Kind regards, -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#946193: workaround
Hi, I removed the timestamp part and bumped down the middle number of LastVersion down by one (to 68.2.0, b/c I had installed 68.3.0) and started Firefox without any problems. -- Miłego dnia, Łukasz Stelmach
Bug#602788: read /sys/class/tty/console/active
Control: tag -1 +patch
Hi,
The attached patch should (I will test it tomorrow) fix the problem.
--
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics
--- live-config-getty-generator.orig 2019-10-22 21:06:50.858966292 +0200
+++ live-config-getty-generator 2019-05-19 10:11:26.0 +0200
@@ -73,9 +73,9 @@
# Configure autologin
if [ -n "${LIVE_USERNAME}" ]
then
- for TTY in tty1 tty2 tty3 tty4 tty5 tty6 $(cat /sys/class/tty/console/active)
+ for NUMBER in $(seq 1 6)
do
- GETTY_SERVICE_D=$SYSTEMD_DIR/getty@${TTY}.service.d
+ GETTY_SERVICE_D=$SYSTEMD_DIR/getty@tty${NUMBER}.service.d
CONF=$GETTY_SERVICE_D/live-config_autologin.conf
mkdir -p $GETTY_SERVICE_D
Bug#936006: Debian 10
The reported problem is not visible (at least not much) on Debian 10. A short investigation suggests it may be a matter of TTF bytecode interpreter version in the freetype library. Apparently in Debian 9, the default version was v35, which when selected in Debian 10 by setting envitonment variable FREETYPE_PROPERTIES="truetype:interpreter-version=35" makes the problem visible again. I will try to choose higher version on a Stretch machine. -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. signature.asc Description: PGP signature
Bug#936006: [Pkg-fonts-devel] Bug#936006: fonts-dejavu-core: Invalid rendering of 'ż' at serveral different sizes
Control: forwarded -1 https://github.com/dejavu-fonts/dejavu-fonts/issues/338 Fabian Greffrath writes: > Would you mind reporting this issue upstream, please? Done, however, I am not 100% sure github is the right place to do it. -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. signature.asc Description: PGP signature
Bug#936006: fonts-dejavu-core: Invalid rendering of 'ż' at serveral different sizes
Package: fonts-dejavu-core Version: 2.37-1 Severity: normal Dear Maintainer, In some applications (notably Firefox) 'ż' (\u017c) character from DejaVu Sans (14px, 16px, 19px, 22px) and DejaVu Serif (15px, 16px) is rendered improperly. The dot above is not centered and there is a pixel or two of extra space to the left of the character. Steps to reproduce: 1. Open the attached zhet.html file in Firefox or 2. Run: xfd -fa 'DejaVu Sans:size=12' -- System Information: Debian Release: 9.9 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information -- Miłego dnia, Łukasz Stelmach zhet.html Description: Binary data
Bug#915395: Info received (A fix for librsvg)
Control: severity -1 minor signature.asc Description: PGP signature
Bug#915403: afew: afew can't handle messages with double quotes in message ids
Package: afew Version: 1.3.0-1 Severity: normal Tags: patch Dear Maintainer, If a message has double quotes in its message id (it's weird, I know), Message-Id: <"foo"@bar> afew can't tag it properly and the message remains tagged as new. This has been fixed upstream[1]. Please backport the patch. [1] https://github.com/afewmail/afew/commit/950bda7cd517c767d6c8cbc7d00ff2df6d7b6d94 -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel, arm64 Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages afew depends on: ii python3 3.5.3-1 ii python3-chardet 2.3.0-2 ii python3-dkim 0.8.1-1~bpo90+1 ii python3-notmuch 0.28-2~bpo9+1 afew recommends no packages. afew suggests no packages. -- no debconf information -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#915395: A fix for librsvg
Hi, For reference, a simmilar problem was discovered and fixed in librsvg quite a while ago. https://bugzilla.gnome.org/show_bug.cgi?id=317615 -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#915395: firefox-esr: Improper use of *printf causes problems with Gtk CSS parsing
Package: firefox-esr
Version: 60.3.0esr-1~deb9u1
Severity: normal
File: /usr/lib/firefox-esr/libxul.so
Dear Maintainer,
When I am starting Firefox with locale set to pl_PL.utf-8 two Gtk
warnings are displayed
--8<---cut here---start->8---
(firefox-esr:9981): Gtk-WARNING **: Theme parsing error: :1:34: Expected
')' in col
or definition
(firefox-esr:9981): Gtk-WARNING **: Theme parsing error: :1:77: Expected
')' in col
or definition
--8<---cut here---end--->8---
They are caused by improperly formatted CSS string passed to
gtk_css_provider_load_from_data function from code within libxul.so
(I uesd ltrace+gdb). The CSS string is
:selected{color:rgba(255,255,255,1,00);background-color:rgba(74,144,217,1,00);
Note that the fourth argument to rgba() is a real number with comma as a
decimal point according to my locale. Running with LC_NUMERIC=C
LC_NUMERIC=C firefox -ProfileManager
makes the problem dissapear. The format strings used to build the CSS
data are in Debian sources in file
firefox-esr-60.3.0esr/widget/gtk/IMContextWrapper.cpp in lines 228 and
239. AppendPrintf() method is implemented in
firefox-esr-60.3.0esr/xpcom/string/nsTSubstring.cpp
Please forward the problem upstream, as it seems the implementation
hasn't changed[1][2] since 60.3.0.
[1]
https://hg.mozilla.org/mozilla-central/file/01d0813d8203/widget/gtk/IMContextWrapper.cpp#l260
[2]
https://hg.mozilla.org/mozilla-central/file/01d0813d8203/xpcom/string/nsTSubstring.cpp#l1203
-- Package-specific info:
-- Addons package information
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: 9.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armel, arm64
Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages firefox-esr depends on:
ii debianutils 4.8.1.1
ii fontconfig2.11.0-6.7+b1
ii libasound21.1.3-5
ii libatk1.0-0 2.22.0-1
ii libc6 2.24-11+deb9u3
ii libcairo-gobject2 1.14.8-1
ii libcairo2 1.14.8-1
ii libdbus-1-3 1.10.26-0+deb9u1
ii libdbus-glib-1-2 0.108-2
ii libevent-2.0-52.0.21-stable-3
ii libffi6 3.2.1-6
ii libfontconfig12.11.0-6.7+b1
ii libfreetype6 2.6.3-3.2
ii libgcc1 1:6.3.0-18+deb9u1
ii libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii libglib2.0-0 2.50.3-2
ii libgtk-3-03.22.11-1
ii libjsoncpp1 1.7.4-3
ii libpango-1.0-01.40.5-1
ii libstartup-notification0 0.12-4+b2
ii libstdc++66.3.0-18+deb9u1
ii libvpx4 1.6.1-3+deb9u1
ii libx11-6 2:1.6.4-3+deb9u1
ii libx11-xcb1 2:1.6.4-3+deb9u1
ii libxcb-shm0 1.12-1
ii libxcb1 1.12-1
ii libxcomposite11:0.4.4-2
ii libxdamage1 1:1.1.4-2+b3
ii libxext6 2:1.3.3-1+b2
ii libxfixes31:5.0.3-1
ii libxrender1 1:0.9.10-1
ii libxt61:1.1.5-1
ii procps2:3.3.12-3+deb9u1
ii zlib1g1:1.2.8.dfsg-5
Versions of packages firefox-esr recommends:
ii libavcodec-extra57 7:3.2.12-1~deb9u1
ii libavcodec546:9.13-1~bpo70+1
ii libavcodec556:10.1-1~bpo70+1
Versions of packages firefox-esr suggests:
ii fonts-lmodern 2.004.5-3
ii fonts-stix [otf-stix] 1.1.1-4
ii libcanberra0 0.30-3
ii libgssapi-krb5-2 1.15-1+deb9u1
ii libgtk2.0-02.24.31-2
ii pulseaudio 10.0-1+deb9u1
-- no debconf information
--
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics
signature.asc
Description: PGP signature
Bug#914891: afew: Backport afew 1.30 to stretch-backports
Package: afew Severity: wishlist Dear Maintainer, I've got notmuch 0.28 installed from stretch-backports repository and would like to use afew linked against libnotmuch5. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel, arm64 Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#914197: less: double-width characters break how -S works
Package: less Version: 481-2.1 Severity: normal Control: -1 notfound 487 Dear Maintainer, less before version 487 improperly detects double-width characters which breaks how -S option works. Wide characters are counted as narrow, eventhough they occupy two cells on a terminal, which makes less stop displaying text too late and the text is wrapped on a terminal. The problem is due to a bug in the mkutable perl script. Please backport at least the fix for mkutable to Debian 9. -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel, arm64 Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages less depends on: ii debianutils 4.8.1.1 ii libc62.24-11+deb9u3 ii libtinfo56.0+20161126-1+deb9u2 less recommends no packages. less suggests no packages. -- no debconf information -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#913413: [PATCH] Map Shift+Win to Menu
It was <2018-11-13 wto 18:26>, when G. Branden Robinson wrote: > At 2018-11-13T10:37:20+0100, Łukasz Stelmach wrote: >> +// Pressing the Shift+Win (left or right, respectively) acts as Menu >> +// while Shift+Win acts as Menu. > > I don't understand this comment; it seems tautologous. > > Shouldn't it be more like: > > // Pressing left or right Win acts as Win, while Shift+Win acts as Menu. > > ? Yes. It was too late apparently (-; -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#913413: +patch
Control: tag -1 + patch
Bug#913413: [PATCH] Map Shift+Win to Menu
---
rules/base.o_s.part | 3 +++
rules/base.xml.in | 18 ++
symbols/altwin | 18 ++
3 files changed, 39 insertions(+)
Patch created against debian-unstable branch of
https://salsa.debian.org/xorg-team/data/xkb-data.git
diff --git a/rules/base.o_s.part b/rules/base.o_s.part
index 505f094..1893ba6 100644
--- a/rules/base.o_s.part
+++ b/rules/base.o_s.part
@@ -10,6 +10,9 @@
altwin:swap_lalt_lwin= +altwin(swap_lalt_lwin)
altwin:swap_alt_win = +altwin(swap_alt_win)
altwin:prtsc_rwin= +altwin(prtsc_rwin)
+ altwin:lwin_menu = +altwin(lwin_menu)
+ altwin:rwin_menu = +altwin(rwin_menu)
+ altwin:win_menu = +altwin(win_menu)
grab:debug = +srvr_ctrl(grab_debug)
grp:switch = +group(switch)
grp:lswitch = +group(lswitch)
diff --git a/rules/base.xml.in b/rules/base.xml.in
index 3a3a9cd..531755c 100644
--- a/rules/base.xml.in
+++ b/rules/base.xml.in
@@ -6789,6 +6789,24 @@
<_description>Win is mapped to PrtSc and the usual Win
+
+
+ altwin:rwin_menu
+ <_description>Map Shift+Right Win to Menu
+
+
+
+
+ altwin:lwin_menu
+ <_description>Map Shift+Left Win to Menu
+
+
+
+
+ altwin:win_menu
+ <_description>Map Shift+Win (left and right) to Menu
+
+
diff --git a/symbols/altwin b/symbols/altwin
index 7240ab8..587c215 100644
--- a/symbols/altwin
+++ b/symbols/altwin
@@ -114,3 +114,21 @@ xkb_symbols "prtsc_rwin" {
replace key { [ Super_R, Super_R ] };
modifier_map Mod4 { , };
};
+
+// Pressing the Shift+Win (left or right, respectively) acts as Menu
+// while Shift+Win acts as Menu.
+partial modifier_keys
+xkb_symbols "win_switch" {
+include "altwin(lwin_menu)"
+include "altwin(rwin_menu)"
+};
+
+partial modifier_keys
+xkb_symbols "rwin_menu" {
+key { [ Super_R, Menu ] };
+};
+
+partial modifier_keys
+xkb_symbols "lwin_menu" {
+key { [ Super_L, Menu ] };
+};
--
2.19.1
Bug#913413: xkb-data: Map Shift+Win to Menu
Package: xkb-data
Version: 2.19-1+deb9u1
Severity: wishlist
File: /usr/share/X11/xkb/symbols/altwin
Dear Maintainer,
My laptop has got only one "Window" key and no Menu keys. I needed to
add the following lines to the altwin file to make the Shift+Win_L
combination act as a Menu key.
--8<---cut here---start->8---
partial modifier_keys
xkb_symbols "lwin_menu" {
key { [ Super_L, Menu ] };
};
--8<---cut here---end--->8---
Most probably the following line may be useful (I haven't tested them)
for others
--8<---cut here---start->8---
// Pressing the Shift+Win (left or right, respectively) acts as Menu
// while Shift+Win acts as Menu.
partial modifier_keys
xkb_symbols "win_switch" {
include "altwin(lwin_menu)"
include "altwin(rwin_menu)"
};
partial modifier_keys
xkb_symbols "rwin_menu" {
key { [ Super_R, Menu ] };
};
--8<---cut here---end--->8---
Apparently also /share/X11/xkb/rules/evdev and (probably)
/usr/share/X11/xkb/rules/base need to be modified by adding
--8<---cut here---start->8---
altwin:lwin_menu = +altwin(rwin_menu)
altwin:rwin_menu = +altwin(rwin_menu)
altwin:win_menu = +altwin(win_menu)
--8<---cut here---end--->8---
next to other altwin declarations.
From this moment on setting altwin:lwin_menu is available as an xkb
option e.g. in /etc/default/keyboard.
-- System Information:
Debian Release: 9.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
--
Było mi bardzo miło. --- Rurku. --- ...
>Łukasz<--- To dobrze, że mnie słuchasz.
signature.asc
Description: PGP signature
Bug#913042: borgbackup: Borg reads password from command line or environment
Package: borgbackup Version: 1.0.9-1 Severity: normal Dear Maintainer, The two ways of delivering a passphrase from an external program to borg (command line, environment) are not secure. Some other processes in the system may access the passphrase via /proc filesystem. The patches[1][2][3] recently merged upstream enables reading passphrases from a file descriptor (e.g. a pipe) prepared by a parent process. [1] https://github.com/borgbackup/borg/commit/c9c1403685fd1b7af8bbd94a88090f2ce35185e8 [2] https://github.com/borgbackup/borg/commit/82e37fbd03ee0722da340952440f1a1e3d1ca925 [3] https://github.com/borgbackup/borg/commit/548355125e554b099f7181fa0627b9dfe9f3830c -- System Information: Debian Release: 9.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel, arm64 Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages borgbackup depends on: ii libacl12.2.52-3+b1 ii libc6 2.24-11+deb9u3 ii liblz4-1 0.0~r131-2+b1 ii libssl1.1 1.1.0f-3+deb9u2 ii python33.5.3-1 ii python3-llfuse 1.2+dfsg-1 ii python3-msgpack0.4.8-1 ii python3-pkg-resources 33.1.1-1 borgbackup recommends no packages. Versions of packages borgbackup suggests: pn borgbackup-doc -- no debconf information -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#908938: [alsa-devel] Bug#908938: alsa-utils: amixer does not unmute pulseaudio
Control: reassign -1 pulseaudio Control: severity -1 minor Clemens Ladisch writes: > In theory, alsamixer and amixer should be able to access the same controls in > the same way. > > Please show the output of "amixer scontrols". > What is the output of the "toggle"/"unmute" commands without "-q"? --8<---cut here---start->8--- $ amixer -c 0 sset Master toggle Simple mixer control 'Master',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 127 Mono: Playback 85 [67%] [-31.50dB] [off] $ amixer -c 0 sset Master toggle Simple mixer control 'Master',0 Capabilities: pvolume pvolume-joined pswitch pswitch-joined Playback channels: Mono Limits: Playback 0 - 127 Mono: Playback 85 [67%] [-31.50dB] [on] $ amixer -c 0 scontrols Simple mixer control 'Master',0 Simple mixer control 'Headphone',0 Simple mixer control 'Speaker+LO',0 Simple mixer control 'PCM',0 Simple mixer control 'IEC958',0 Simple mixer control 'IEC958',1 Simple mixer control 'IEC958',2 Simple mixer control 'Beep',0 Simple mixer control 'Capture',0 Simple mixer control 'Auto-Mute Mode',0 Simple mixer control 'Digital',0 Simple mixer control 'Dock Mic',0 Simple mixer control 'Dock Mic Boost',0 Simple mixer control 'Headset Mic',0 Simple mixer control 'Headset Mic Boost',0 Simple mixer control 'Internal Mic Boost',0 Simple mixer control 'Loopback Mixing',0 --8<---cut here---end--->8--- OK, -c0 means amixer is accessing the hardware instead of PulseAudio. (Somehow I have assumed PA is selectable via -c, my mistake.) Without -c the output is simpler. --8<---cut here---start->8--- $ amixer scontrols Simple mixer control 'Master',0 Simple mixer control 'Capture',0 --8<---cut here---end--->8--- This is PulseAudio. Indeed, when I run alsamixer -c0 and see the hardware (previously I wasn't specifing -c0), the Master is unmuted properly. However, Speker+LO (which is muted by the first toggle) is not unmuted. I believe, this is a problem with PulseAudio rather than with ALSA. Unmuting both Master and Speaker+LO hardware channels makes PA unmute master. amixer without -c mutes and unmutes PA as expected. Thank you for helping to figure all this stuff out. -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. signature.asc Description: PGP signature
Bug#908938: [WORKAROUND] alsa-utils: amixer does not unmute pulseaudio
Dnia September 16, 2018 6:00:46 PM UTC, Elimar Riesebieter napisał(a): >* Łukasz Stelmach [2018-09-16 17:56 +0200]: > >> Łukasz Stelmach writes: > >> The following command can be used as a workaround >> >> pactl set-sink-mute 0 toggle > >How do you unmute then? Both commands above, amixer and pactl, toggle (change the state to opposite) muting. Only amixer is somehow unable to flip from 'muted' to 'unmuted' properly. Hence, this report. -- Łukasz Stelmach z podróży
Bug#908938: [WORKAROUND] alsa-utils: amixer does not unmute pulseaudio
Łukasz Stelmach writes: > Elimar Riesebieter writes: >> * Łukasz Stelmach [2018-09-16 11:23 +0200]: >>> I've got PulseAudio running, so amixer (and alsamixer) controls the >>> default PA output. I use the following command to control muting of >>> audio. >>> >>> amixer -q -c 0 sset Master toggle The following command can be used as a workaround pactl set-sink-mute 0 toggle -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. signature.asc Description: PGP signature
Bug#908938: [Pkg-alsa-devel] Bug#908938: alsa-utils: amixer does not unmute pulseaudio
Elimar Riesebieter writes: > * Łukasz Stelmach [2018-09-16 11:23 +0200]: > >> I've got PulseAudio running, so amixer (and alsamixer) controls the >> default PA output. I use the following command to control muting of >> audio. >> >> amixer -q -c 0 sset Master toggle >> >> It mutes the audio but can't unmute. Neither can >> >> amixer -q -c 0 sset Master unmute > > Master toggle mutes the Speaker here. so > > amixer -q -c 0 sset Speaker unmute > > does the job on my system. This is a bit confusing users.www On my system Master is the only playback control visible in alsamixer (which is toggled properly with the `m' key). So amixer -q -c 0 sset Speaker unmute simply refuses to do anything amixer: Unable to find simple control 'Speaker',0 There seem to be some subtle difference between alsamixer and amixer which makes makes the former work both ways. > Should we forward this bug to alsa-devel? I believe so. Previously (w/o PA) it worked fine so I have the toggle amixer command bound to the mute key. Please feel free to ask for any further info about my system. -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. signature.asc Description: PGP signature
Bug#908938: alsa-utils: amixer does not unmute pulseaudio
Package: alsa-utils Version: 1.1.3-1 Severity: normal Dear Maintainer, I've got PulseAudio running, so amixer (and alsamixer) controls the default PA output. I use the following command to control muting of audio. amixer -q -c 0 sset Master toggle It mutes the audio but can't unmute. Neither can amixer -q -c 0 sset Master unmute Only alsamixer and pavucontrol can unmute. -- System Information: Debian Release: 9.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages alsa-utils depends on: ii kmod 23-2 ii libasound21.1.3-5 ii libc6 2.24-11+deb9u3 ii libfftw3-single3 3.3.5-3 ii libncursesw5 6.0+20161126-1+deb9u2 ii libsamplerate00.1.8-8+b2 ii libtinfo5 6.0+20161126-1+deb9u2 ii lsb-base 9.20161125 ii whiptail 0.52.19-1+b1 alsa-utils recommends no packages. alsa-utils suggests no packages. -- no debconf information -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. signature.asc Description: PGP signature
Bug#902816: mini-httpd: mini-httpd fails to stop upon "systemctl top"
Package: mini-httpd
Version: 1.23-1.2
Severity: important
Dear Maintainer,
1. I started mini-httpd with "systemctl start mini-httpd"
2. I tried to stop it with "systemctl stop mini-httpd"
3. The process was still running. Among other log messages ther was this
one
start-stop-daemon: warning: this system is not able to track process names
longer than 15 characters, please use --exec instead of --name.
4. I expected mini-httpd to stop after "systemctl stop" command.
To fix the problem, the following patch for /etc/init.d/mini-httpd is
required.
--8<---cut here---start->8---
--- a/etc/init.d/mini-httpd 2018-07-01 17:10:15.354864914 +0200
+++ b/etc/init.d/mini-httpd 2018-07-01 17:10:31.079301238 +0200
@@ -60,7 +60,7 @@
fi
fi
else
- start-stop-daemon --stop --quiet --oknodo --name $DAEMON
+ start-stop-daemon --stop --quiet --oknodo --exec $DAEMON
fi
echo "$NAME."
}
--8<---cut here---end--->8---
-- System Information:
Debian Release: 9.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-6-amd64 (SMP w/4 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages mini-httpd depends on:
ii libc6 2.24-11+deb9u3
ii libssl1.1 1.1.0f-3+deb9u2
Versions of packages mini-httpd recommends:
pn apache2-utils
mini-httpd suggests no packages.
-- Configuration Files:
/etc/default/mini-httpd changed:
START=1
DAEMON_OPTS="-C /etc/mini-httpd.conf"
/etc/init.d/mini-httpd changed:
set -x
. /lib/lsb/init-functions
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/mini_httpd
NAME=mini_httpd
DESC="web server"
PIDFILE=/var/run/mini_httpd.pid
test -x $DAEMON || exit 0
if [ -f /etc/default/mini-httpd ]
then
. /etc/default/mini-httpd
fi
set -e
start() {
if [ "$START" = "1" ]
then
echo -n "Starting $DESC: "
start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
--exec $DAEMON -- $DAEMON_OPTS
echo "$NAME."
else
printf "You have to edit /etc/mini-httpd.conf
and\n/etc/default/mini-httpd before running mini-httpd!\n"
printf " "
exit 0
fi
}
stop() {
echo -n "Stopping $DESC: "
# Get pid number
if [ -e /var/run/$NAME.pid ]
then
PID=`cat /var/run/$NAME.pid`
if [ -d /proc/$PID ]
then
start-stop-daemon -v --stop --quiet --oknodo --pidfile
/var/run/$NAME.pid
else
# we need to remove the pidfile manually
if [ -e /var/run/$NAME.pid ]
then
rm -f /var/run/$NAME.pid
fi
fi
else
start-stop-daemon --stop --quiet --oknodo --exec $DAEMON
fi
echo "$NAME."
}
case "$1" in
start)
start
;;
stop)
stop
;;
status)
status_of_proc -p $PIDFILE $DAEMON $NAME && exit 0 || exit $?
;;
restart|force-reload)
stop
start
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|status|restart|force-reload}" >&2
exit 1
;;
esac
exit 0
/etc/mini-httpd.conf changed:
ssl
host=zniczek.stlmch.eu
port=80
user=nobody
nochroot # no
data_dir=/var/www/html
cgipat=cgi-bin/*
certfile=/etc/ssl/private/mini-httpd.cert
logfile=/var/log/mini-httpd.log
pidfile=/var/run/mini-httpd.pid
charset=iso-8859-1
-- no debconf information
--
Było mi bardzo miło. --- Rurku. --- ...
>Łukasz<--- To dobrze, że mnie słuchasz.
signature.asc
Description: PGP signature
Bug#892729: awesome: programs are slow to respond to kestrokes and mouse buttons)
It was <2018-04-28 sob 10:40>, when Reiner Herrmann wrote: > On Thu, Apr 19, 2018 at 10:13:16AM +0200, Łukasz Stelmach wrote: >> All this makes me think that the X server (or the video driver) has some >> problems with some timers (poll/epoll/select?) which should wake it up >> but don't. Even though it appears this isn't necessarily a bug in >> awesome, it doesn't appear under openbox. I will soon check other window >> managers too. > > Thanks for all your investigations on this issue! > Unfortunately I don't see this issue on my systems, but it sounds to me > also related to something deeper than awesome. Unfortunately I don't know the X and driver code well enough to find the offending code by just looking at the output of strace. I even wouldn't be surprised if there was a hardware issue. > It would be interesting to know if this also happens with newer > X/kernel/video drivers/awesome from unstable. But you probably have > a reason for running stable. I'd love to help, but this is my desktop machine ;-) If there are any other information I can provide, please tell. > What GPU and video drivers are you using? It is xserver-xorg-video-intel 2:2.99.917+git20161206-1, see the attached log for details. PS. I haven't had any issues since started unagi. -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics [312573.762] X.Org X Server 1.19.2 Release Date: 2017-03-02 [312573.762] X Protocol Version 11, Revision 0 [312573.762] Build Operating System: Linux 4.9.0-4-amd64 x86_64 Debian [312573.762] Current Operating System: Linux AMDC1062 4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02) x86_64 [312573.762] Kernel command line: initrd=/boot/initrd.img-4.9.0-6-amd64 root=UUID=f52fdabb-9a8b-4a87-b89e-dbb3aecbcb8b ro init=/lib/systemd/systemd resume=/dev/sda3 BOOT_IMAGE=/boot/vmlinuz-4.9.0-6-amd64 [312573.762] Build Date: 16 October 2017 08:19:45AM [312573.762] xorg-server 2:1.19.2-1+deb9u2 (https://www.debian.org/support) [312573.762] Current version of pixman: 0.34.0 [312573.762]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [312573.762] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [312573.762] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 19 11:00:26 2018 [312573.762] (==) Using config file: "/etc/X11/xorg.conf" [312573.762] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [312573.762] (==) ServerLayout "XSrv" [312573.762] (**) |-->Screen "Screen0" (0) [312573.762] (**) | |-->Monitor "Front" [312573.762] (**) | |-->Device "Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)" [312573.762] (**) | |-->GPUDevice "My Card" [312573.762] (**) | |-->GPUDevice "Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)" [312573.762] (**) | |-->GPUDevice "NVIDIA Corporation GF108 [GeForce GT 430] (rev a1)" [312573.762] (**) |-->Input Device "Mouse0" [312573.762] (==) Automatically adding devices [312573.762] (==) Automatically enabling devices [312573.762] (==) Automatically adding GPU devices [312573.762] (==) Max clients allowed: 256, resource mask: 0x1f [312573.763] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [312573.763]Entry deleted from font path. [312573.763] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [312573.763] (==) ModulePath set to "/usr/lib/xorg/modules" [312573.763] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [312573.763] (II) Loader magic: 0x5602f5641e00 [312573.763] (II) Module ABI versions: [312573.763]X.Org ANSI C Emulation: 0.4 [312573.763]X.Org Video Driver: 23.0 [312573.763]X.Org XInput driver : 24.1 [312573.763]X.Org Server Extension : 10.0 [312573.763] (++) using VT number 7 [312573.764] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [312573.764] (II) xfree86: Adding drm device (/dev/dri/card0) [312573.777] (--) PCI:*(0:0:2:0) 8086:0102:1028:047e rev 9, Mem @ 0xe0c0/4194304, 0xd000/268435456, I/O @ 0x3000/64, BIOS @ 0x/131072 [312573.777] (II) LoadModule: "glx" [312573.777] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [312573.77
Bug#891997: libcurl3: NO_PROXY doesn't work for IPv6 literals
Package: libcurl3 Version: 7.52.1-5+deb9u4 Severity: normal Dear Maintainer, There is a bug in libcurl that makes it ignore IPv6 numeric addresses in the NO_PROXY environment variable. It impossible to make libcurl connect to, for example http://[::1], if http_proxy is set. The bug is being fixed upstream. Please see https://github.com/curl/curl/issues/2353 for details. -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libcurl3 depends on: ii libc6 2.24-11+deb9u1 ii libcomerr21.43.4-2 ii libgssapi-krb5-2 1.15-1+deb9u1 ii libidn2-0 0.16-1+deb9u1 ii libk5crypto3 1.15-1+deb9u1 ii libkrb5-3 1.15-1+deb9u1 ii libldap-2.4-2 2.4.44+dfsg-5+deb9u1 ii libnghttp2-14 1.18.1-1 ii libpsl5 0.17.0-3 ii librtmp1 2.4+20151223.gitfa8646d.1-1+b1 ii libssh2-1 1.7.0-1 ii libssl1.0.2 1.0.2l-2+deb9u2 ii zlib1g1:1.2.8.dfsg-5 Versions of packages libcurl3 recommends: ii ca-certificates 20161130+nmu1 libcurl3 suggests no packages. -- no debconf information -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. pgpMhxaQqQBRh.pgp Description: PGP signature
Bug#890849: golang-1.8-go: Environment not set, go command not found
Package: golang-1.8-go Version: 1.8.1-1 Severity: normal Dear Maintainer, After installing golang-1.8-go (via golang-1.8) the go command is not available. $ go bash: go: command not found golang-1.8-go apparently provides neither: * files in /etc/profile.d * alternatives * a wrapper in /usr/bin to check the environment and help user set it up. Users need to set up their environment (PATH, GOPATH) manually. Unfortunatelly this isn't well documented either. Neither golang-1.8-doc nor golang-1.8-go provide a short README file with instructions how to do it. -- System Information: Debian Release: 9.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages golang-1.8-go depends on: ii golang-1.8-src 1.8.1-1 ii libc6 2.24-11+deb9u1 Versions of packages golang-1.8-go recommends: ii g++ 4:6.3.0-4 ii gcc 4:6.3.0-4 ii libc6-dev 2.24-11+deb9u1 ii pkg-config 0.29-4+b1 Versions of packages golang-1.8-go suggests: pn bzr ii ca-certificates 20161130+nmu1 ii git 1:2.11.0-3+deb9u2 pn mercurial pn subversion -- no debconf information -- Kind regards, Łukasz Stelmach pgpsGRZwXAvCh.pgp Description: PGP signature
Bug#889734: libjson-xs-perl: JSON::XS is broken in multithreaded programs
Package: libjson-xs-perl
Version: 3.030-1
Severity: important
Dear Maintainer,
The following program exposes a bug in JSON::XS module which makes the
program die.
--8<---cut here---start->8---
#!/usr/bin/perl
use JSON;
use threads;
my $thnum = int($ARGV[0]);
$href{"foo"} = "bar";
for (1..$thnum) {
threads->create(sub { print "quick thread\n" });
}
foreach (threads->list()) { $_->join(); }
print to_json(\%href);
--8<---cut here---end--->8---
For any number of threads other than 0 (e.g. "perl prog.pl 1") the
program dies printing[1]
hash- or arrayref expected (not a simple scalar, use allow_nonref to allow
this) at /usr/share/perl5/JSON.pm line 156.
The logic that triggers it is in json_nonref()[2]. The condition that
causes the function to return 1 is[3]
SvSTASH (scalar) == bool_stash
because bool_stash is 0! bool_stash is assigned a value twice. Once in
BOOT[4] and for the second time in CLONE[5], which appears to be a problem.
Note, that to_json() dies even in the main thread.
[1]
https://anonscm.debian.org/git/pkg-perl/packages/libjson-xs-perl.git/tree/XS.xs#n961
[2]
https://anonscm.debian.org/git/pkg-perl/packages/libjson-xs-perl.git/tree/XS.xs#n356
[3]
https://anonscm.debian.org/git/pkg-perl/packages/libjson-xs-perl.git/tree/XS.xs#n365
[4]
https://anonscm.debian.org/git/pkg-perl/packages/libjson-xs-perl.git/tree/XS.xs#n1999
[5]
https://anonscm.debian.org/git/pkg-perl/packages/libjson-xs-perl.git/tree/XS.xs#n2014
-- System Information:
Debian Release: 9.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: armel, arm64
Kernel: Linux 4.9.0-0.bpo.5-amd64 (SMP w/8 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libjson-xs-perl depends on:
ii libc6 2.24-11+deb9u1
ii libcommon-sense-perl3.74-2
ii libtypes-serialiser-perl1.0-1
ii perl5.24.1-3+deb9u2
ii perl-base [perlapi-5.24.1] 5.24.1-3+deb9u2
libjson-xs-perl recommends no packages.
libjson-xs-perl suggests no packages.
-- no debconf information
--
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics
signature.asc
Description: PGP signature
Bug#886940: libzypp-dev: ZyppCommon.cmake is installed in a wrong directory
Package: libzypp-dev Version: 14.29.1-2 Severity: normal Dear Maintainer, It appears the ZyppCommon.cmake file is installed in a wrong directory. When I try to build https://github.com/openSUSE/libzypp-bindings I get an error messagage --8<---cut here---start->8--- CMake Error at CMakeLists.txt:20 (INCLUDE): include could not find load file: ZyppCommon --8<---cut here---end--->8--- the workaround I've found is to copy the file to /usr/share/cmake-3.6/Modules/. -- System Information: Debian Release: 8.10 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: armel, arm64 Kernel: Linux 4.9.0-0.bpo.5-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libzypp-dev depends on: ii libzypp 14.29.1-2 libzypp-dev recommends no packages. libzypp-dev suggests no packages. -- no debconf information -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#861178: nodejs-dev: broken/uninstallable backports
Control: merge -1 862962 The problem still exists in 4.8.2~dfsg-1~bpo8+1 and apt-cache shows nodejs-dev depends on libssl1.0-dev. --8<---cut here---start->8--- Package: nodejs-dev Source: nodejs Version: 4.8.2~dfsg-1~bpo8+1 Installed-Size: 1329 Maintainer: Debian Javascript Maintainers <pkg-javascript-de...@lists.alioth.debian.org> Architecture: amd64 Depends: python, libssl1.0-dev (>= 1.0.2), libuv1-dev, nodejs (= 4.8.2~dfsg-1~bpo8+1) Suggests: debhelper Description-en: evented I/O for V8 javascript (development files) Node.js is a platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications. Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. . This package is needed to build plugins. Description-md5: 80f21f18dc84266acebc6380c27c1a79 Homepage: http://nodejs.org/ Section: devel Priority: extra Filename: pool/main/n/nodejs/nodejs-dev_4.8.2~dfsg-1~bpo8+1_amd64.deb Size: 542522 MD5sum: 3b277f24adfb67645ae44635591b9e1f SHA1: cd900450cfa347fcb8fc8e906e5f8ba8d49e5175 SHA256: 958109c14622d919d76dc72f0af8334fa34b10471971baef757cd34fb795535f --8<---cut here---end--->8--- I've filed a bug[1] that probably deserves merging with this one. Please unmerge if you think it does not. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862962 -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#862962: nodejs-dev: Unable to install nodejs-dev 4.7.2~dfsg-2~bpo8+1
Package: nodejs-dev Version: 4.7.2~dfsg-2~bpo8+1 Severity: important Dear Maintainer, I can't install the nodejs-dev package from jessie-backports. Apparently, the package has invalid dependency on libssl1.0-dev which is not available in any jessie repository[1]. [1] https://packages.debian.org/search?keywords=libssl1.0-dev -- System Information: Debian Release: 8.8 APT prefers stable-updates APT policy: (950, 'stable-updates'), (950, 'stable'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: armel, arm64 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#862389: [Pkg-xfce-devel] Bug#862389: lightdm: X gets locked up after several switches to VT
It was <2017-05-12 pią 17:54>, when Yves-Alexis Perez wrote: > On Fri, 2017-05-12 at 09:54 +0200, Łukasz Stelmach wrote: >> I had reported[1] this problem to the lighdm mailing list but there was no >> response. >> >> [1] https://lists.freedesktop.org/archives/lightdm/2017-March/001056.html > > Can you please open a bug on launchpad? Mailing lists are more for discussion > purposes I think. Done. https://bugs.launchpad.net/lightdm/+bug/1690739 -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#862389: X gets locked up after several switches to VT
I've rebuilt lightdm 1.18.3-1 from Stretch on my Jessie desktop and
after a few VT-to-X switches some data is still stuck between lightdm
and X.
--8<---cut here---start->8---
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
u_str ESTAB 3840* 20164523 *
20167969 users:(("lightdm",pid=21965,fd=11))
u_str ESTAB 0 9216 @/tmp/.X11-unix/X0 20167969 *
20164523 users:(("Xorg",pid=21969,fd=18))
--8<---cut here---end------->8---
--
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics
signature.asc
Description: PGP signature
Bug#862389: lightdm: X gets locked up after several switches to VT
Package: lightdm
Version: 1.10.3-3
Severity: normal
Dear Maintainer,
After I had switched from X to VT several times (maybe there are other
cuases too, but I don't know them) X stopped updating windows. The mouse
cursor was moving and changing its shape as I moved it over different
windows. I could still switch betwen VT and X. On VT I found that,
apparently, lightdm wan't handling data from X properly because there
was over 200kB worth of data waiting in X's send queue and 8k in receive
queue in lightdm.
--8<---cut here---start->8---
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
u_str ESTAB 0 213504 @/tmp/.X11-unix/X0 9689907 * 9691709
users:(("Xorg",pid=11405,fd=18))
u_str ESTAB 8896 0* 9691709 * 9689907
users:(("lightdm",pid=10124,fd=11))
--8<---cut here---end--->8---
The numbers had been growing each time I switched between X and VT.
I had reported[1] this problem to the lighdm mailing list but there was no
response.
[1] https://lists.freedesktop.org/archives/lightdm/2017-March/001056.html
-- System Information:
Debian Release: 8.8
APT prefers stable-updates
APT policy: (950, 'stable-updates'), (950, 'stable'), (500,
'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: armel, arm64
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lightdm depends on:
ii adduser3.113+nmu3
ii consolekit 0.4.6-5
ii dbus 1.8.22-0+deb8u1
ii debconf [debconf-2.0] 1.5.56
ii libc6 2.19-18+deb8u9
ii libgcrypt201.6.3-2+deb8u2
ii libglib2.0-0 2.42.1-1+b1
ii libpam-systemd 215-17+deb8u7
ii libpam0g 1.1.8-3.1+deb8u2
ii libxcb11.10-3+b1
ii libxdmcp6 1:1.1.1-1+b1
ii lightdm-gtk-greeter [lightdm-greeter] 1.8.5-2
Versions of packages lightdm recommends:
ii xserver-xorg 1:7.7+7
Versions of packages lightdm suggests:
ii accountsservice 0.6.37-3+b1
ii upower 0.99.1-3.2
-- Configuration Files:
/etc/apparmor.d/lightdm-guest-session 9d3af5806375ac868fcaf5aaf3d56a00 [Errno
2] Nie ma takiego pliku ani katalogu: u'/etc/apparmor.d/lightdm-guest-session
9d3af5806375ac868fcaf5aaf3d56a00'
/etc/init/lightdm.conf b5de8ae57f7a4f102b6a6943139957a5 [Errno 2] Nie ma
takiego pliku ani katalogu: u'/etc/init/lightdm.conf
b5de8ae57f7a4f102b6a6943139957a5'
-- debconf information:
lightdm/daemon_name: /usr/sbin/lightdm
* shared/default-x-display-manager: lightdm
--
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics
signature.asc
Description: PGP signature
Bug#860871: libjson-c-doc: the package contains no html files
Package: libjson-c-doc Version: 0.11-4 Severity: normal Dear Maintainer, The libjson-c-doc package contains no HTML files in the. /usr/share/doc/libjson-c-doc/html directory which makes it useless. -- System Information: Debian Release: 8.7 APT prefers stable-updates APT policy: (950, 'stable-updates'), (950, 'stable'), (500, 'proposed-updates') Architecture: amd64 (x86_64) Foreign Architectures: armel, arm64 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libjson-c-doc depends on: ii libjs-jquery 1.7.2+dfsg-3.2 libjson-c-doc recommends no packages. libjson-c-doc suggests no packages. -- no debconf information -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics
Bug#856476: [PATCH] Add support for starting other window managers in Debian menu
---
debian/awesome.menu-method | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/debian/awesome.menu-method b/debian/awesome.menu-method
index 4d81d78..06dbc50 100644
--- a/debian/awesome.menu-method
+++ b/debian/awesome.menu-method
@@ -18,10 +18,12 @@ function findicon($filename)=
function x11menu()= "\t{"q(title())","q($command) ifnempty($icon,
","findicon($icon))"},\n";
function textmenu()= "\t{"q(title())", \"x-terminal-emulator -e
\".."q($command) ifnempty($icon,
","findicon($icon))"},\n";
+function wmmenu()= "\t{"q(title())",function () awesome.exec("q($command)")
end" ifnempty($icon, ","findicon($icon))"},\n";
supported;
x11= x11menu();
text= textmenu();
+wm= wmmenu();
endsupported;
startmenu= "Debian_menu[\""s($section)"\"] = {\n";
@@ -31,4 +33,4 @@ genmenu="debian/menu.lua";
rootsection="Debian";
rootprefix= "/etc/xdg/awesome/";
userprefix= shell("echo -n /${XDG_CONFIG_HOME-.config}") "/awesome/";
-preoutput= "-- automatically generated file. Do not edit (see
/usr/share/doc/menu/html)\n\nmodule(\"debian.menu\")\n\nDebian_menu = {}\n\n";
+preoutput= "-- automatically generated file. Do not edit (see
/usr/share/doc/menu/html)\n\nlocal awesome =
awesome\nmodule(\"debian.menu\")\n\nDebian_menu = {}\n\n";
--
2.1.4
Bug#856476: awesome: Debian menu in awesome does not show other window managers
Package: awesome
Version: 3.4.15-1+b1
Severity: normal
Control: tags -1 + patch
Dear Maintainer,
The Debian menu in awesome does not containe entries for running other
window managers. This is because /etc/menu-methods/awesome doesn't have
wm defined in the supported section. As far as I can tell it is also a
problem in the latest version of the package.
My patch will follow this message as soon as it gets bug number.
-- System Information:
Debian Release: 8.7
APT prefers stable-updates
APT policy: (950, 'stable-updates'), (950, 'stable'), (500,
'proposed-updates')
Architecture: amd64 (x86_64)
Foreign Architectures: armel, arm64
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages awesome depends on:
ii dbus-x11 1.8.22-0+deb8u1
ii libc6 2.19-18+deb8u7
ii libcairo2 1.14.0-2.1+deb8u2
ii libdbus-1-3 1.8.22-0+deb8u1
ii libev41:4.15-3
ii libglib2.0-0 2.42.1-1+b1
ii libimlib2 1.4.6-2+deb8u2
ii liblua5.1-0 5.1.5-7.1
ii libpango1.0-0 1.36.8-3
ii libstartup-notification0 0.12-4
ii libx11-6 2:1.6.2-3
ii libx11-xcb1 2:1.6.2-3
ii libxcb-icccm4 0.4.1-1
ii libxcb-image0 0.4.0-1
ii libxcb-keysyms1 0.4.0-1
ii libxcb-randr0 1.10-3+b1
ii libxcb-render01.10-3+b1
ii libxcb-shape0 1.10-3+b1
ii libxcb-shm0 1.10-3+b1
ii libxcb-util0 0.3.8-3
ii libxcb-xinerama0 1.10-3+b1
ii libxcb-xtest0 1.10-3+b1
ii libxcb1 1.10-3+b1
ii libxcursor1 1:1.1.14-1+b1
ii libxdg-basedir1 1.2.0-1
ii menu 2.1.47
Versions of packages awesome recommends:
ii feh2.12-1
ii rlwrap 0.41-1
ii x11-xserver-utils 7.7+3+b1
awesome suggests no packages.
-- Configuration Files:
/etc/menu-methods/awesome changed:
compat="menu-1"
!include menu.h
compat="menu-2"
outputencoding= "UTF-8";
function q($s) = "\"" esc($s,"\\\"") "\"";
function s($s) = replacewith(replacewith($s,"/","_"), " ", "_");
function findicon($filename)=
ifelsefile($filename, q($filename),
iffile("/usr/share/pixmaps/" $filename,
q("/usr/share/pixmaps/" $filename)));
function x11menu()= "\t{"q(title())","q($command) ifnempty($icon,
","findicon($icon))"},\n";
function textmenu()= "\t{"q(title())", \"x-terminal-emulator -e
\".."q($command) ifnempty($icon,
","findicon($icon))"},\n";
function wmmenu()= "\t{"q(title())",function () awesome.exec("q($command)")
end" ifnempty($icon, ","findicon($icon))"},\n";
supported;
x11= x11menu();
text= textmenu();
wm= wmmenu();
endsupported;
startmenu= "Debian_menu[\""s($section)"\"] = {\n";
endmenu="}\n";
submenutitle= "\t{ "q(title())", Debian_menu[\""s($section)"\"] },\n";
genmenu="debian/menu.lua";
rootsection="Debian";
rootprefix= "/etc/xdg/awesome/";
userprefix= shell("echo -n /${XDG_CONFIG_HOME-.config}") "/awesome/";
preoutput= "-- automatically generated file. Do not edit (see
/usr/share/doc/menu/html)\n\nlocal awesome =
awesome\nmodule(\"debian.menu\")\n\nDebian_menu = {}\n\n";
-- no debconf information
--
Łukasz Stelmach
Samsung R Institute Poland
Samsung Electronics
signature.asc
Description: PGP signature
Bug#852478: make: Implicit rule for yacc does not handle the header file
Package: make Version: 4.0-8.1 Severity: normal Dear Maintainer, I created a parser.y and scanner.l files. I included parser.h in scanner.l. I created Makefile with the following contentc --8<---cut here---start->8--- LEX = flex LFLAGS = -I YACC = bison YFLAGS = -d -y --8<---cut here---end--->8--- Running make(1) make parser.c causes the following commands to be executed bison -d -y parser.y mv -f y.tab.c parser.c but y.tab.h is not renamed to parser.h as I expected. It appears the implicit rule, compiled into make(1), ignores the fact that yacc(1) can generate headers. It is possible to work around this problem by defining custom rules but I'd expect make(1) to rename the generated header file (if it exists) as well with built-in rules. -- System Information: Debian Release: 8.7 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages make depends on: ii libc6 2.19-18+deb8u7 make recommends no packages. Versions of packages make suggests: ii make-doc 4.0-2 -- no debconf information -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. pgpm5ibLLLHOD.pgp Description: PGP signature
Bug#845376: debian-installer: don't add "swap" flag in crypttab if pasword is not random
Package: debian-installer Severity: normal Dear Maintainer, I installed Debian (8.6) on a laptop. I created two encrypted partition. One for the root filesystem and the I marked in partman to be used as swap. I chose not to use /dev/urandom as keyfile because I wanted the swap to hold hibernation image. One of the flags in the fourth field in crypttab for the swap partition is "swap". I am afraid (I haven't tested it) that boot scripts would run mkswap and erase hibernation image. The "swap" flag in the crypttab set only if one chooses to use random password. -- System Information: Debian Release: 8.6 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. pgptZPGMe7Rq0.pgp Description: PGP signature
Bug#835080: debian-installer: Preseeding of ESSID is impossible, apparently
Package: debian-installer Severity: normal Dear Maintainer, This may be a bug in netcfg or debconf but because I encounter it during installation I will file it here. I have tried preseeding the name of my WiFi network (ESSID) by providing different combinations of values for netcfg/wireles_show_essids and netcfg/wireles_essid. | case no. | w_s_e | w_e | |--+-+-| |0 | -unset- | -unset- | |1 | my_net | -unset- | |2 | -unset- | my_net | |3 | manual | my_net | 0. The default case. I am presented with a list and able to choose my_net on it. 1. I get the list of nets in the air with my_net highlighted. I still need to press [Enter] to continue (BUG). 2. Looks like 0. 3. Looks like 1, except the "Manual" option is highlighted on the list. (BUG) I expected that setting ESSID in preseed.cfg like d-i netcfg/wireless_essid string my_net would prevent presenting me a list of available networks and make the installer connect to the one I had set. If I were to guess what is wrong I'd say netcfg_wireless_show_essids() doesn't handle preseeding correctly like netcfg_get_interface() does. -- System Information: Debian Release: 8.5 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. pgpSbbpR1fHnx.pgp Description: PGP signature
Bug#835073: debian-installer: Allow preseeding WPA preshared-key with wpa_passphrase
Package: debian-installer Severity: wishlist Dear Maintainer, I am creating preseed.cfg for several of my machines. Some of them are connected via WiFi so I'd like to provide credentials automatically. It is possible to set passphrase in netcfg/wireless_wpa but I'd rather provide a PSK as generated by wpa_passphrase(8). -- System Information: Debian Release: 8.5 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. pgpzbdYPlULAH.pgp Description: PGP signature
Bug#835062: debain-installer: Preseeding of ESSID is impossible, apparently
Package: debain-installer Severity: normal Dear Maintainer, This may be a bug in netcfg or debconf but because I encounter it during installation I will file it here. I have tried preseeding the name of my WiFi network (ESSID) by providing different combinations of values for netcfg/wireles_show_essids and netcfg/wireles_essid. | case no. | w_s_e | w_e | |--+-+-| |0 | -unset- | -unset- | |1 | my_net | -unset- | |2 | -unset- | my_net | |3 | manual | my_net | 0. The default case. I am presented with a list and able to choose my_net on it. 1. I get the list of nets in the air with my_net highlighted. I still need to press [Enter] to continue (BUG). 2. Looks like 0. 3. Looks like 1, except the "Manual" option is highlighted on the list. (BUG) I expected that setting ESSID in preseed.cfg like d-i netcfg/wireless_essid string my_net would prevent presenting me a list of available networks and make the installer connect to the one I had set. If I were to guess what is wrong I'd say netcfg_wireless_show_essids() doesn't handle preseeding correctly like netcfg_get_interface() does. -- System Information: Debian Release: 8.5 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. pgp9_6hHEFQW2.pgp Description: PGP signature
Bug#834641: debian-installer: Mount arbitrary device according boot parameters
Package: debian-installer Severity: wishlist Dear Maintainer, please add a boot parameter to make debian-installer mount an arbitrary devices in arbitrary directories of the debian-installer tmpfs. For example, passing (something like): d-i.mount=/dev/disk/by-uuid/dead-beef:/firmware might help solving the problem I have described in bug #834267. Another scenario is providing preseed.cfg without remastering the hybrid ISO image "burnt" on a USB stick that still holds a lot of free space to add another partition with e.g. preseed.cfg without remastering the ISO filesystem. * It should be possible to refer to a partition with a stable name (by-path, by-uuid) rather than only sdX. * It should be possible to pass an arbitrary number of mounts * Filesystems should be mounted quite early so they can hold data for preseed/early_command. -- System Information: Debian Release: 8.5 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. pgpwrVH2I5piR.pgp Description: PGP signature
Bug#834267: debian-installer: d-i can't find firmware on the second usb stick (jessie)
Package: debian-installer Severity: normal Dear Maintainer, I have booted debian-installer from a USB stick with the hybrid ISO image. I was requested to provide wifi firmware files. I have recorded them on another stick and plugged it in. Unfortunately the installer can't find them. As far as I cen tell the problem is in the mountmedia script which appears to mount the first device returned by its devlist function. In my case it is the main partition on the d-i USB stick. To work around this problem copied the firmware package into /firmware of the running installer. -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz.
Bug#819703: xscreensaver: please upgrade the package
Dear Maintainer, please update the xscreensaver package in both Jessie and Wheezy. Thak you, -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#816826: emacs24: ps-print produces invalid PostScript output
Package: emacs24 Version: 24.4+1-5 Severity: normal Dear Maintainer, Under some circumstances ps-print module produces invalid PostScript code that fails to print or display. Please see my bug report and a patch upstream[1] and consider applying the patch to emacs24. [1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=22611 -- System Information: Debian Release: 8.3 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages emacs24 depends on: ii emacs24-bin-common 24.4+1-5 ii gconf-service 3.2.6-3 ii libacl12.2.52-2 ii libasound2 1.0.28-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-18+deb8u2 ii libcairo-gobject2 1.14.0-2.1 ii libcairo2 1.14.0-2.1 ii libdbus-1-31.8.20-0+deb8u1 ii libfontconfig1 2.11.0-6.3 ii libfreetype6 2.5.2-3+deb8u1 ii libgconf-2-4 3.2.6-3 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u4 ii libgif44.1.6-11+deb8u1 ii libglib2.0-0 2.42.1-1+b1 ii libgnutls-deb0-28 3.3.8-6+deb8u3 ii libgomp1 4.9.2-10 ii libgpm21.20.4-6.1+b2 ii libgtk-3-0 3.14.5-1+deb8u1 ii libice62:1.0.9-1+b1 ii libjpeg62-turbo1:1.3.1-12 ii libm17n-0 1.6.4-3 ii libmagickcore-6.q16-2 8:6.8.9.9-5+deb8u1 ii libmagickwand-6.q16-2 8:6.8.9.9-5+deb8u1 ii libotf00.9.13-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libpng12-0 1.2.50-2+deb8u2 ii librsvg2-2 2.40.5-1 ii libselinux12.3-2 ii libsm6 2:1.2.2-1+b1 ii libtiff5 4.0.3-12.3+deb8u1 ii libtinfo5 5.9+20140913-1+b1 ii libx11-6 2:1.6.2-3 ii libxft22.3.2-1 ii libxinerama1 2:1.1.3-1+b1 ii libxml22.9.1+dfsg1-5+deb8u1 ii libxpm41:3.5.11-1+b1 ii libxrandr2 2:1.4.2-1+b1 ii libxrender11:0.9.8-1+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 emacs24 recommends no packages. Versions of packages emacs24 suggests: ii emacs24-common-non-dfsg 24.4+1-2 -- no debconf information -- Miłego dnia, Łukasz Stelmach
Bug#814013: systemd: systemd-cryptsetup-generator doesn't work well with passdev in crypttab
Package: systemd Version: 215-17+deb8u3 Severity: normal Dear Maintainer, I've discovered that systemd-cryptsetup-generator doesn't work well in Debian. It seems that the reason is the way Debina abuses/extends the meaning of the third column of /etc/crypttab. By definition: The third field, key file, describes the file to use as a key for decrypting the data of the source device. Note that the entire key file will be used as the passphrase; the passphrase must not be followed by a newline character. To enable storing of key file on portable/pluggable device Debian provides passdev which accepts an extended format of the filed which includes a device node and a file name separated by a colon. systemd-cryptsetup-generator recognises such file name as a device name altogether and makes the respective cryptsetup unit depend on a nonexsitent device. For example, in my crypttab I've got the following entry: crypt-root UUID=9c9f0311-2647-4bfc-abcd-516edbd99363 /dev/disk/by-uuid/0396339f-904a-42d7-abcd-95d5549bff94:/key_root luks,keyscript=passdev the respective unit refers to an invalid device (see After and Requires fields). As the device never appears I need to wait for 90 seconds for a timeout. --8<---cut here---start->8--- # Automatically generated by systemd-cryptsetup-generator [Unit] Description=Cryptography Setup for %I Documentation=man:crypttab(5) man:systemd-cryptsetup-generator(8) man:systemd-cryptsetup@.service(8) SourcePath=/etc/crypttab DefaultDependencies=no Conflicts=umount.target BindsTo=dev-mapper-%i.device IgnoreOnIsolate=true After=systemd-readahead-collect.service systemd-readahead-replay.service cryptsetup-pre.target Before=cryptsetup.target After=dev-disk-by\x2duuid-0396339f\x2d904a\x2d42d7\x2dabcd\x2d95d5549bff94:-key_root.device Requires=dev-disk-by\x2duuid-0396339f\x2d904a\x2d42d7\x2abcd5\x2d95d5549bff94:-key_root.device BindsTo=dev-disk-by\x2duuid-9c9f0311\x2d2647\x2d4bfc\x2dabcd\x2d516edbd99363.device After=dev-disk-by\x2duuid-9c9f0311\x2d2647\x2d4bfc\x2dabcd\x2d516edbd99363.device Before=umount.target [Service] Type=oneshot RemainAfterExit=yes TimeoutSec=0 ExecStart=/lib/systemd/systemd-cryptsetup attach 'crypt-root' '/dev/disk/by-uuid/9c9f0311-2647-4bfc-abcd-516edbd99363' '/dev/disk/by-uuid/0396339f-904a-42d7-abcd-95d5549bff94:/key_root' 'luks,keyscript=passdev' ExecStop=/lib/systemd/systemd-cryptsetup detach 'crypt-root' --8<---cut here---end--->8--- systemd-cryptsetup does not know about passdev as a means of obtaining a password so it won't understand the reference to the /dev/disk/by-uuid/03[...]ff94:/key_root file either. One way to work around this bug is to mask systemd-cryptsetup@crypt\x2droot.service. It won't hurt because the root filesystem has already been mounted by initramfs. -- Package-specific info: -- BEGIN ATTACHMENTS -- /tmp/tmp.P1MDMTgfSx/systemd-delta.txt /tmp/tmp.P1MDMTgfSx/systemd-analyze-dump.txt /tmp/tmp.P1MDMTgfSx/dsh-enabled.txt /etc/fstab -- END ATTACHMENTS -- -- System Information: Debian Release: 8.3 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-586 Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18+deb8u2 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2+b3 ii libpam0g1.1.8-3.1+deb8u1 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u3 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev215-17+deb8u3 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus1.8.20-0+deb8u1 ii libpam-systemd 215-17+deb8u3 Versions of packages systemd suggests: pn systemd-ui -- no debconf information -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz.
Bug#805223: base-installer unable to determine kernel
Dnia 10 grudnia 2015 18:50:00 CET, Martin Michlmayr <t...@cyrius.com> napisał(a): >* Łukasz Stelmach <steel...@post.pl> [2015-11-16 10:16]: >> I will try the fix suggested by Martin Michlmayr and see if it works. > >Did it work? Due to personal reasons I haven't had time to verify it yet. -- Łukasz Stelmach z podróży
Bug#805223: base-installer unable to determine kernel
Dnia 15 listopad 2015 o 22:54 Ben Hutchings <b...@decadent.org.uk> napisał(a): > On Sun, 2015-11-15 at 22:17 +0100, Łukasz Stelmach wrote: >> During the installation I get a message that the installer was unable to >> find appropriate kernel package for the device. >> >> No installable kernel was found in the defined APT sources. [...] >> >> I have traced the the message and it comes from pick_kernel() in >> /usr/lib//base-installer/library.sh. In /var/log/syslog I find a message >> >> Jan 1 00:52:06 base-installer: info: could not determine kernel flavour >> >> repeated several times and followed by >> >> Jan 1 00:52:06 base-installer: info: Found kernels '' >> >> A very brief investigation suggests that that the problems comes from >> the references to unassigned $FLAVOUR variable. > > Unassigned, or empty? It's hard to tell precisely. FLAVOUR is not assigned any value in library.sh explicitly AND "$FLAVOUR" apparently evaluates to "" at line 352[1]. >> I may only suspect that >> the code containing $FLAVOUR has been moved from some file without >> moving actual assignment (like the one in >> debian/bootstrap-base.postinst) > [...] > > These functions are only ever called by debian/bootstrap-base.postinst. > I think the problem is that arch_get_kernel_flavour is failing. I have never said they are. I only gave the postinst script as an example of a place where FLAVOUR is assigned. Do you know of any other place? > This definitely doesn't seem like a proper fix. Then what is in your opinion KERNEL_FLAVOUR for? It can't but ask why there are two variables with apparently the same value (or at least values from the same set). I will try the fix suggested by Martin Michlmayr and see if it works. [1] https://sources.debian.net/src/base-installer/1.154/library.sh/#L352 -- Miłego dnia, Łukasz Stelmach
Bug#805223: base-installer unable to determine kernel
Package: base-installer
Version: 1.154
Tags: patch
Dear Maintainer,
I am trying to install Debian jessie on an arm device (Zyxel NSA325).
The device isn't yet officially supported by d-i and I had to make some
changes to d-i to run it on the device. I am willing to share my work as
soon as possible.
During the installation I get a message that the installer was unable to
find appropriate kernel package for the device.
No installable kernel was found in the defined APT sources. [...]
I have traced the the message and it comes from pick_kernel() in
/usr/lib//base-installer/library.sh. In /var/log/syslog I find a message
Jan 1 00:52:06 base-installer: info: could not determine kernel flavour
repeated several times and followed by
Jan 1 00:52:06 base-installer: info: Found kernels ''
A very brief investigation suggests that that the problems comes from
the references to unassigned $FLAVOUR variable. I may only suspect that
the code containing $FLAVOUR has been moved from some file without
moving actual assignment (like the one in
debian/bootstrap-base.postinst)
The attached patch renames occurrences of $FLAVOUR in library.sh to
$KERNEL_FLAVOUR. A quick in vitro test in a d-i shell
--8<---cut here---start->8---
. /usr/lib/base-installer/kernel.sh
. /usr/lib/base-installer/library.sh;
kernel_update_list
cat /tmp/available_kernels.txt
--8<---cut here---end--->8---
returns expected results:
--8<---cut here---start->8---
linux-image-kirkwood
linux-image-3.16.0-4-kirkwood
--8<---cut here---end--->8---
and the installer presents a nice list of available containing the two
above and a "none" option.
--
Było mi bardzo miło. --- Rurku. --- ...
>Łukasz<--- To dobrze, że mnie słuchasz.
... Droga wśród jabłoni prowadzi w nieznane...
From 6885bbfe670ab48bdbc65a127331a7f380b71a59 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C5=81ukasz=20Stelmach?= <steel...@post.pl>
Date: Sun, 15 Nov 2015 21:54:08 +0100
Subject: [PATCH] Rename $FLAVOUR to $KERNEL_FLAVOUR
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Signed-off-by: Łukasz Stelmach <steel...@post.pl>
---
library.sh | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/library.sh b/library.sh
index d73d880..cfb0f6f 100644
--- a/library.sh
+++ b/library.sh
@@ -349,12 +349,12 @@ kernel_update_list () {
cut -d" " -f1 | grep -v "linux-image-2.6" | uniq > "$KERNEL_LIST.unfiltered"
kernels=`sort -r "$KERNEL_LIST.unfiltered" | tr '\n' ' ' | sed -e 's/ $//'`
for candidate in $kernels; do
- if [ -n "$FLAVOUR" ]; then
- if arch_check_usable_kernel "$candidate" "$FLAVOUR"; then
+ if [ -n "$KERNEL_FLAVOUR" ]; then
+ if arch_check_usable_kernel "$candidate" "$KERNEL_FLAVOUR"; then
echo "$candidate"
-info "kernel $candidate usable on $FLAVOUR"
+info "kernel $candidate usable on $KERNEL_FLAVOUR"
else
-info "kernel $candidate not usable on $FLAVOUR"
+info "kernel $candidate not usable on $KERNEL_FLAVOUR"
fi
else
info "could not determine kernel flavour"
@@ -404,8 +404,8 @@ pick_kernel () {
# Unset seen flag in case we had an incorrect preseeded value.
db_fset base-installer/kernel/image seen false || true
- if [ -n "$FLAVOUR" ]; then
- arch_kernel="$(arch_get_kernel "$FLAVOUR")"
+ if [ -n "$KERNEL_FLAVOUR" ]; then
+ arch_kernel="$(arch_get_kernel "$KERNEL_FLAVOUR")"
# Hack to support selection of meta packages with a postfix
# added to the normal name (for updated kernels in stable).
--
2.4.6
signature.asc
Description: PGP signature
Bug#803711: copy:// urls ommited in gen-sources.list.udeb
Package: debian-installer
Version: 20150422+deb8u2
Tags: patch
I've debootstrapped a chroot from a local debian mirror. The
sources.list file in the chroot is
deb file:///srv/debian jessie main
deb file:///srv/debian jessie-proposed-updates main
but the gen-sources.list.udeb script outputs only
deb copy:///srv/debian jessie main/debian-installer
The script has some elaborate code to handle (f|ht)tp urls and add
proposed-updates when needed for those but can't handle file:/// urls
and ouptputs only one repo instead of two. The attached patch fixes the
problem in a rather simplistic yet efficient way.
Kind regards,
--
Było mi bardzo miło. --- Rurku. --- ...
>Łukasz<--- To dobrze, że mnie słuchasz.
...Przez ulicę przechodzi na żółtym świetle, jabłka obiera żyletką, lubi ryzyko
diff --git a/build/util/gen-sources.list.udeb b/build/util/gen-sources.list.udeb
index 26a0ac2..7f62d9d 100755
--- a/build/util/gen-sources.list.udeb
+++ b/build/util/gen-sources.list.udeb
@@ -86,6 +86,9 @@ for mirror in $MIRRORS; do
fi
else
echo "$mirror $SUITE $UDEB_COMPONENTS"
+ if [ "$USE_PROPOSED_UPDATES" = 1 ]; then
+ echo "$mirror $SUITE-proposed-updates $UDEB_COMPONENTS"
+ fi
fi
done | perl -ne 'print unless $seen{$_}; $seen{$_}=1'
signature.asc
Description: PGP signature
Bug#801810: Passwords are not hashed with MD5 anymore (Appendix B)
Source: installation-guide Version: 20150423+deb8u1 Tags: patch In the section 4.5[1] of Appendix B there are several references to "MD5 hash" as a method of storing passwords. At the end of the section there is a reference to mkpasswd command generating SHA-512 crypt(3) hash. Hence, the hashes should be refered to as "crypt(3) hashes" rather than MD5. Furthermore, the following sentence Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks. while true, is not actually relevant for crypt(3) hashes based on stronger hashes like SHA-256 or SHA-512. I attach a patch for english version of the guide. -- Było mi bardzo miło. --- Rurku. --- ... >Łukasz<--- To dobrze, że mnie słuchasz. ... Od tej pory wszystko może się zdarzyć. Akcja toczy się... Index: en/appendix/preseed.xml === --- en/appendix/preseed.xml (revision 70042) +++ en/appendix/preseed.xml (working copy) @@ -999,7 +999,7 @@ The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear -text values or MD5 hashes. +text values or crypt(3) hashes. @@ -1006,9 +1006,9 @@ Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these -passwords. Using MD5 hashes is considered slightly better in terms of -security but it might also give a false sense of security as access to a -MD5 hash allows for brute force attacks. +passwords. Storing hashed passwords is considered secure unless a weak +hashing algorithm like DES or MD5 is used which allow for bruteforce +attacks. Recommended password hashing algorithms are SHA-256 and SHA512. @@ -1022,8 +1022,8 @@ # Root password, either in clear text #d-i passwd/root-password password r00tme #d-i passwd/root-password-again password r00tme -# or encrypted using an MD5 hash. -#d-i passwd/root-password-crypted password [MD5 hash] +# or encrypted using an crypt(3) hash. +#d-i passwd/root-password-crypted password [crypt(3) hash] # To create a normal user account. #d-i passwd/user-fullname string Debian User @@ -1031,8 +1031,8 @@ # Normal user's password, either in clear text #d-i passwd/user-password password insecure #d-i passwd/user-password-again password insecure -# or encrypted using an MD5 hash. -#d-i passwd/user-password-crypted password [MD5 hash] +# or encrypted using an crypt(3) hash. +#d-i passwd/user-password-crypted password [crypt(3) hash] # Create the first user with the specified UID instead of the default. #d-i passwd/user-uid string 1010 @@ -1054,7 +1054,7 @@ The following command (available from the whois package) -can be used to generate an MD5 hash for a password: +can be used to generate an SHA-512 based crypt(3) hash for a password: mkpasswd -m sha-512 signature.asc Description: PGP signature
Bug#784634: rdesktop: rdesktop fails to connect, segmentation fault
Package: rdesktop Version: 1.8.2-3 Severity: grave Dear Maintainer, I have upgraded from wheezy to jessie recently including rdesktop package. After the upgrade I can't connect to Windows 7 virtual machine. All I get is the Segmentation fault message. I checked out the latest version from upstream svn (t1847, 1.8.3 + 8 commits), built it with the same options as the Debian package and it does not crash. There is still some issue because rdeskto tries to log in and I get Invalid user name message but it is still better than a crash. I bisected the history between r1806 and r1847. r1824 fixes my problem. --8---cut here---start-8--- r1824 | hean01 | 2014-08-27 14:15:21 +0200 (śro) | 4 linie Fix sigsegv while using credssp and kerberos without specifying domainname as argument. --8---cut here---end---8--- -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (990, 'stable-updates'), (900, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages rdesktop depends on: ii libasound21.0.28-1 ii libc6 2.19-18 ii libgssglue1 0.4-2 ii libpcsclite1 1.8.13-1 ii libssl1.0.0 1.0.1k-3 ii libx11-6 2:1.6.2-3 ii libxrandr22:1.4.2-1+b1 rdesktop recommends no packages. Versions of packages rdesktop suggests: pn pcscd none -- no debconf information -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#775564: emacs24: emacs fails to byte-compile apel and org-mode
Package: emacs24 Version: 24.4+1-4.1~bpo70+1 Severity: important Dear Maintainer, I've just upgraded emacs24 on my Debian wheezy machine and the package fails to configure itself. The actual reason is that it can't byte-compile some files from apel (10.8-2) and org-mode (8.0.7-2~bpo70+1) packages. See the attached log files. I have found a piece of hint that might be helpful in solving this problem here: http://thread.gmane.org/gmane.emacs.orgmode/77532 -- System Information: Debian Release: 7.8 APT prefers stable-updates APT policy: (990, 'stable-updates'), (900, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel Kernel: Linux 3.16-0.bpo.3-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages emacs24 depends on: ii emacs24-bin-common 24.4+1-4.1~bpo70+1 ii gconf-service 3.2.5-1+build1 ii libacl1 2.2.51-8 ii libasound2 1.0.25-4 ii libatk1.0-0 2.4.0-2 ii libc6 2.13-38+deb7u6 ii libcairo-gobject2 1.12.2-3 ii libcairo2 1.12.2-3 ii libdbus-1-3 1.6.8-1+deb7u5 ii libfontconfig1 2.9.0-7.1 ii libfreetype62.4.9-1.1 ii libgconf-2-43.2.5-1+build1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libgif4 4.1.6-10 ii libglib2.0-02.33.12+really2.32.4-5 ii libgnutls-deb0-28 3.3.8-4~bpo70+1 ii libgomp14.7.2-5 ii libgpm2 1.20.4-6 ii libgtk-3-0 3.4.2-7 ii libice6 2:1.0.8-2 ii libjpeg88d-1+deb7u1 ii libm17n-0 1.6.3-2 ii libmagickcore5 8:6.7.7.10-5+deb7u3 ii libmagickwand5 8:6.7.7.10-5+deb7u3 ii libotf0 0.9.12-2 ii libpango1.0-0 1.30.0-1 ii libpng12-0 1.2.49-1 ii librsvg2-2 2.36.1-2 ii libselinux1 2.1.9-5 ii libsm6 2:1.2.1-2 ii libtiff43.9.6-11 ii libtinfo5 5.9-10 ii libx11-62:1.5.0-1+deb7u1 ii libxft2 2.3.1-1 ii libxinerama12:1.1.2-1+deb7u1 ii libxml2 2.8.0+dfsg1-7+wheezy2 ii libxpm4 1:3.5.10-1 ii libxrandr2 2:1.3.2-2+deb7u1 ii libxrender1 1:0.9.7-1+deb7u1 ii zlib1g 1:1.2.7.dfsg-13 emacs24 recommends no packages. Versions of packages emacs24 suggests: ii emacs24-common-non-dfsg 24.1+1-1 -- no debconf information emacs24 -q -no-site-file -batch -l __myinit.el -f batch-byte-compile alist.el apel-ver.el atype.el broken.el calist.el emu.el file-detect.el filename.el install.el inv-19.el inv-23.el invisible.el mcharset.el mcs-20.el mcs-e20.el mule-caesar.el path-util.el pccl-20.el pccl.el pces-20.el pces-e20.el pces.el pcustom.el poe.el poem-e20_3.el poem-e20.el poem.el product.el pym.el richtext.el static.el tinycustom.el Loading `static': old-style backquotes detected! Loading `pym': old-style backquotes detected! Loading `product': old-style backquotes detected! Wrote /usr/share/emacs24/site-lisp/apel/alist.elc Wrote /usr/share/emacs24/site-lisp/apel/apel-ver.elc Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: atype.el:28:1:Error: Wrong type argument: sequencep, 769 Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: broken.el:28:1:Error: Wrong type argument: sequencep, 769 Wrote /usr/share/emacs24/site-lisp/apel/calist.elc Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: emu.el:27:1:Error: Wrong type argument: sequencep, 769 Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: file-detect.el:34:1:Error: Wrong type argument: sequencep, 769 Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: filename.el:28:1:Error: Wrong type argument: sequencep, 769 Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: install.el:29:1:Error: Wrong type argument: sequencep, 769 Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: inv-19.el:27:1:Error: Wrong type argument: sequencep, 769 Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: inv-23.el:28:1:Error: Wrong type argument: sequencep, 769 Wrote /usr/share/emacs24/site-lisp/apel/invisible.elc Eager macro-expansion failure: (wrong-type-argument sequencep 769) Loading `poe': old-style backquotes detected! In toplevel form: mcharset.el:27:1:Error: Wrong type argument: sequencep, 769 Wrote /usr/share/emacs24/site-lisp/apel/mcs-20.elc Eager macro-expansion
Bug#774647: cryptsetup on initramfs does not support key files (resume swap on LVM)
Package: cryptsetup Version: 2:1.4.3-4 Severity: normal Dear Maintainer, I have the following setup (see below for the files) + /boot on /dev/sda1 + root filesystem on /dev/mapper/sda2_cryptblk + /home, /var and swap on LVM on /dev/mapper/sdb2_crypt --- blkid --- /dev/mapper/vg1-home: LABEL=HOME UUID=3c300542 TYPE=ext4 /dev/mapper/vg1-var: LABEL=VAR UUID=c4be931f TYPE=ext4 /dev/mapper/vg1-swap: LABEL=swap UUID=cb8020c2 TYPE=swap - sda2_crypt is protected by a password I enter upon boot-up, sdb2_crypt with a key file stored on the root filesystem. I added resume=UUID=... pointing to my swap to the kernel command line and ran update-initramfs and got the following message cryptsetup: WARNING: target sdb2_crypt uses a key file, skipped Apparently the cryptsetup initramfs scripts do not support my case where a key file for a partition is stored on another encrypted partition. A simmilar use case has been described here: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/238163 -- Package-specific info: -- /proc/cmdline initrd=/initrd.img-3.2.0-4-amd64 root=/dev/mapper/sda2_crypt ro quiet resume=UUID=cb8020c2 BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 -- /etc/crypttab sda2_crypt UUID=2646df90 none luks sdb2_crypt UUID=06e17a3e /root/sdb2.key luks -- /etc/fstab # file system mount point type options dump pass /dev/mapper/sda2_crypt/ ext4noatime,errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=abb3bb32 /boot ext2noatime,nodev,nosuid,noexec 0 2 UUID=c4be931f /varext4defaults,noatime,errors=remount-ro 0 2 UUID=3c300542 /home ext4defaults,noatime,errors=remount-ro 0 2 UUID=cb8020c2 noneswapdefaults 0 0 -- lsmod Module Size Used by parport_pc 22364 0 ppdev 12763 0 lp 17149 0 parport31858 3 lp,ppdev,parport_pc rfcomm 33700 0 bnep 17567 2 bluetooth 119455 10 bnep,rfcomm binfmt_misc12957 1 uinput 17440 1 nfsd 216181 2 nfs 308353 0 nfs_acl12511 2 nfs,nfsd auth_rpcgss37143 2 nfs,nfsd fscache36739 1 nfs lockd 67306 2 nfs,nfsd sunrpc173730 6 lockd,auth_rpcgss,nfs_acl,nfs,nfsd ext3 162072 1 jbd56902 1 ext3 ext2 59231 1 loop 22641 0 adt747521744 0 hwmon_vid 12430 1 adt7475 snd_hda_codec_realtek 188851 1 joydev 17266 0 arc4 12458 2 ath9k 64619 0 nouveau 583385 3 ath9k_common 12728 1 ath9k ath9k_hw 322112 2 ath9k_common,ath9k snd_hda_intel 26259 2 snd_hda_codec 78031 2 snd_hda_intel,snd_hda_codec_realtek ath21370 3 ath9k_hw,ath9k_common,ath9k video 17683 1 nouveau mac80211 192806 1 ath9k snd_hwdep 13186 1 snd_hda_codec ttm53664 1 nouveau psmouse69265 0 snd_pcm68083 2 snd_hda_codec,snd_hda_intel drm_kms_helper 31370 1 nouveau cfg80211 137243 3 mac80211,ath,ath9k snd_page_alloc 13003 2 snd_pcm,snd_hda_intel drm 183952 5 drm_kms_helper,ttm,nouveau snd_seq45126 0 rfkill 19012 5 cfg80211,bluetooth snd_seq_device 13176 1 snd_seq snd_timer 22917 2 snd_seq,snd_pcm mxm_wmi12515 1 nouveau evdev 17562 12 power_supply 13475 1 nouveau i2c_algo_bit 12841 1 nouveau snd52893 12 snd_timer,snd_seq_device,snd_seq,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_realtek coretemp 12898 0 pcspkr 12579 0 serio_raw 12931 0 soundcore 13065 1 snd i2c_i801 16870 0 i7core_edac22454 0 iTCO_wdt 17081 0 i2c_core 23876 6 i2c_i801,i2c_algo_bit,drm,drm_kms_helper,nouveau,adt7475 iTCO_vendor_support12704 1 iTCO_wdt edac_core 35258 3 i7core_edac button 12937 1 nouveau wmi13243 2 mxm_wmi,nouveau processor 28149 0 ext4 350763 3 crc16 12343 2 ext4,bluetooth jbd2 62115 1 ext4 mbcache13114 3 ext4,ext2,ext3 cryptd 14517 0 aes_x86_64 16843 33 aes_generic33026 1 aes_x86_64 xts12645 16 gf128mul 13048 1 xts dm_crypt 22586 2 dm_mod 63645 14 dm_crypt raid1 30714 1 md_mod
Bug#774566: extlinux: remove resume= option from kernel command-line for recovery mode
Package: extlinux Version: 2:4.05+dfsg-6+deb7u1 Severity: minor Dear Maintainer, extlinux-update creates recovery mode entries by adding single and removing quiet options in kernel command line. I think there may be some other options that should be removed too. For example, resume=... because it is quite tricky (rescue shell after resuming) or dangerous to do anything with the system before resuming. It might be convenient to have separate entry without resume= option and without single too. -- System Information: Debian Release: 7.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages extlinux depends on: ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u6 Versions of packages extlinux recommends: ii os-prober 1.58 ii syslinux-common 2:4.05+dfsg-6+deb7u1 ii syslinux-themes-debian 11-1.1 extlinux suggests no packages. -- debconf information: * extlinux/install: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#772855: installation-reports: unable to connect to a wifi network on channel 13
Package: installation-reports Severity: important Dear Maintainer, I downloaded Debian 7.7 installation image[1]. I followed the installation procedure and chose wlan0 networki interface when asked to configure the primary network interface. Then there was no WLAN on the list of availble networks. It appeared after I changed channel on my AP from 13 to 1. I suspect the reason of this problem MAY be the default regulatory settings of wifi stack/card driver in the Linux kernel if it is prepared for the USA where, according to Wikipedia[2], the channel may be used only under certain conditions. [1] debian-7.7.0-amd64-i386-netinst.iso (md5 afc576c3886f9abab9ba886c4cd51a88) [2] https://en.wikipedia.org/wiki/List_of_WLAN_channels -- Było mi bardzo miło. --- Rurku. --- ... Łukasz--- To dobrze, że mnie słuchasz. ... Od tej pory wszystko może się zdarzyć. Akcja toczy się... signature.asc Description: PGP signature
Bug#749084: Wikipedia and Amazon favicons
Hi, It seams that neither Wikipedia nor Amazon provide their favicons in PNG format like DuckDuckGo does, so it is not possible to patch their searchengine files like I did with DDG's[1]. While it is possible to include PNG file as base64 encoded data: URL, I don't think the sites (especially Amazon) would be very glad (or maybe not) Debian distributes their copyrighted artwork. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762429#20 -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgpfmdqh5Z4Vl.pgp Description: PGP signature
Bug#762429: [PATCH] Use PNG icon instead of ICO
For some reason the browser has issues with displaying search engine's
icon in ICO format.
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762429
---
debian/duckduckgo.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debian/duckduckgo.xml b/debian/duckduckgo.xml
index 6d614a3..0dd2c2c 100644
--- a/debian/duckduckgo.xml
+++ b/debian/duckduckgo.xml
@@ -2,7 +2,7 @@
ShortNameDuckDuckGo/ShortName
DescriptionDuckDuckGo Search/Description
InputEncodingUTF-8/InputEncoding
-Image width=16 height=16
type=image/x-iconhttps://duckduckgo.com/favicon.ico/Image
+Image width=16 height=16
type=image/pnghttps://duckduckgo.com/favicon.png/Image
Url type=text/html method=GET template=https://duckduckgo.com/;
Param name=q value={searchTerms}/
Param name=t value=debian/
--
1.9.1
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container
It was 2014-07-08 wto 21:34, when Michael Biebl wrote: Am 08.07.2014 17:50, schrieb Łukasz Stelmach: It was 2014-07-08 wto 16:29, when Michael Biebl wrote: Am 08.07.2014 16:03, schrieb Michael Biebl: I can not reproduce this but I have to add that my host is running Debian sid with 204-14. The container was created as per your instructions. Have you bind-mounted /run or /dev/(shm) into the container? Actually, this is most likely a kernel issue. [...] Please update your kernel to the version from backports if you want to run systemd-nspawn and report back. Now I am running 3.12.9-1~bpo70+1 kernel and I cannot log into container. All I get is: login[96]: FAILED LOGIN (1) on '/dev/console' FOR 'root', System error Tomorrow I will try 3.14. I've setup a test-environment with 3.12 as kernel and could reproduce your issue. An upgrade to 3.14 did fix it for me. Indeed, 3.14.7-1~bpo70+1 works fine. Do you think I should report problems with 3.12? -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgpNBGuhxDD9v.pgp Description: PGP signature
Bug#754158: blueman: blueman-applet says pulseaudio is too old
It was 2014-07-08 wto 21:37, when Christopher Schramm wrote: this is a known problem of the wheezy version. As you mentioned you can use the backports version to make it work. What's the intention of your bug report? (Disclaimer: I am quite new to Debain an I know little about release and QA procedures so please bare with me) To fix the problem in wheezy, IMHO it isn't good to have a broken piece of software in the stable release and as far as I can tell it seems quite easy to fix it. -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgp0GoK2ZjKfh.pgp Description: PGP signature
Bug#754193: linux-image-3.2.0-4-amd64: reboot(2) called from a PID namespace shuts down a host
It was 2014-07-08 wto 18:30, when Ben Hutchings wrote: On Tue, 2014-07-08 at 16:33 +0200, Łukasz Stelmach wrote: Package: src:linux Version: 3.2.60-1+deb7u1 Severity: normal Dear Maintainer, tl;dr: init in a container (PID namespace) can call reboot(2) and shutdown the host machine. Yes, and you need real user namespaces (as introduced in Linux 3.7) to prevent this. It does not *seem* the so on 3.14-0.bpo.1-amd64: --8---cut here---start-8--- # ls -l /proc/1/ns total 0 lrwxrwxrwx 1 root root 0 Jul 9 10:39 ipc - ipc:[4026531839] lrwxrwxrwx 1 root root 0 Jul 9 10:39 mnt - mnt:[4026531840] lrwxrwxrwx 1 root root 0 Jul 9 10:39 net - net:[4026531968] lrwxrwxrwx 1 root root 0 Jul 9 10:39 pid - pid:[4026531836] lrwxrwxrwx 1 root root 0 Jul 9 10:39 user - user:[4026531837] lrwxrwxrwx 1 root root 0 Jul 9 10:39 uts - uts:[4026531838] # ls -l /proc/2572/ns/ total 0 lrwxrwxrwx 1 root root 0 Jul 9 10:34 ipc - ipc:[4026532358] lrwxrwxrwx 1 root root 0 Jul 9 10:34 mnt - mnt:[4026532356] lrwxrwxrwx 1 root root 0 Jul 9 10:34 net - net:[4026531968] lrwxrwxrwx 1 root root 0 Jul 9 10:34 pid - pid:[4026532359] lrwxrwxrwx 1 root root 0 Jul 9 10:34 user - user:[4026531837] lrwxrwxrwx 1 root root 0 Jul 9 10:34 uts - uts:[4026532357] --8---cut here---end---8--- PID 2572 is a contained systemd and it works in the same user (and net) namespace as PID 1. Please refer to [1] for a detailed description of symptoms. After some investigation and thanks to help received from systemd developers I can tell the problems can be solved by applying [2] to the kernel. The patch is relatively old, it has been released only three months after 3.2.0 so I hope applying it wouldn't be a problem. [...] This change seems to make containers work better, but it does not improve security. I'm not sure whether this is sufficient justification for a stable update. Please can you ask the stable release team (debian-rele...@lists.debian.org) to consider this. Sent. -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgpZTbHl0c92W.pgp Description: PGP signature
Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container
It was 2014-07-09 śro 13:24, when Michael Biebl wrote: Am 09.07.2014 10:20, schrieb Łukasz Stelmach: It was 2014-07-08 wto 21:34, when Michael Biebl wrote: Am 08.07.2014 17:50, schrieb Łukasz Stelmach: It was 2014-07-08 wto 16:29, when Michael Biebl wrote: Am 08.07.2014 16:03, schrieb Michael Biebl: I can not reproduce this but I have to add that my host is running Debian sid with 204-14. The container was created as per your instructions. Have you bind-mounted /run or /dev/(shm) into the container? Actually, this is most likely a kernel issue. [...] Please update your kernel to the version from backports if you want to run systemd-nspawn and report back. Now I am running 3.12.9-1~bpo70+1 kernel and I cannot log into container. All I get is: login[96]: FAILED LOGIN (1) on '/dev/console' FOR 'root', System error Tomorrow I will try 3.14. I've setup a test-environment with 3.12 as kernel and could reproduce your issue. An upgrade to 3.14 did fix it for me. Indeed, 3.14.7-1~bpo70+1 works fine. Do you think I should report problems with 3.12? I'm not sure it's worth it. After all, the kernel team already provides a 3.14 backport so they are unlikely to spend time on the 3.12 backports kernel. Are you ok with closing this bug report? I don't think there is anything to do from the systemd side here. Yes. Thak you for your attention and assistance. -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgp0Aw56JbpvR.pgp Description: PGP signature
Bug#754158: blueman: blueman-applet says pulseaudio is too old
It was 2014-07-09 śro 14:57, when Christopher Schramm wrote: I'm absolutely with you. Unfortunately stable branches only receive security related bug fixes. Users may get new features or functional bug fixes only through other branches like backports. OK, I am not the one to decide and I accept Debian's got its rules, however, in my humble opinion anything called stable shouldn't ship software that does work at all and backports sources (as far as I remember) are not configured in apt by default. OK, I've got blueman from backports and I've got backports in my sources (actually I had it for quite some time but I set its priority low not to get updates from there automatically) *and* thaks to you I've learnt that I should always check backports (I am still somewhat reluctant to accepting backported versions automatically, am I wrong). All this probably means that this report isn't relevant any more and should be closed. Kind regards, -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgpRacWy3xmQC.pgp Description: PGP signature
Bug#754158: blueman: blueman-applet says pulseaudio is too old
Package: blueman Version: 1.23-1 Severity: grave Dear Maintainer, blueman-applet fails to start and prints the following message --8---cut here---start-8--- blueman-applet version 1.22 starting Using gconf config backend Using gconf config backend Using gconf config backend Using gconf config backend Using gconf config backend Using gconf config backend Using gconf config backend Using gconf config backend Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/blueman/plugins/BasePlugin.py, line 65, in _load self.on_load(parent) File /usr/lib/python2.7/dist-packages/blueman/plugins/applet/PulseAudio.py, line 173, in on_load raise Exception(PulseAudio too old, required 0.9.15 or higher) Exception: PulseAudio too old, required 0.9.15 or higher Using gconf config backend Using gconf config backend Using gconf config backend Deleting plugin instance blueman.plugins.applet.PulseAudio.PulseAudio object at 0x2eab150 --8---cut here---end---8--- It looks like the code in PulseAudio.py that checks the version number is too simple --8---cut here---start-8--- if version[2] 15: raise Exception(PulseAudio too old, required 0.9.15 or higher) --8---cut here---end---8--- The version reported by the blueman.main.PulseAudioUtils module is [4, 0, 0] --8---cut here---start-8--- Python 2.7.3 (default, Mar 13 2014, 11:03:55) [GCC 4.7.2] on linux2 Type help, copyright, credits or license for more information. from blueman.main.PulseAudioUtils import PulseAudioUtils, EventType foo=PulseAudioUtils() _ pa_context_event (/usr/lib/python2.7/dist-packages/blueman/main/PulseAudioUtils.py:159) 1 _ pa_context_event (/usr/lib/python2.7/dist-packages/blueman/main/PulseAudioUtils.py:159) 5 foo.GetVersion() [4, 0, 0] --8---cut here---end---8--- The problem is fiexed in the trunk version of blueman http://bazaar.launchpad.net/~blueman/blueman/trunk/view/head:/blueman/plugins/applet/PulseAudio.py#L180 as well as 1.23-git201312311147-1~bpo70+1 in wheezy-backports. -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (990, 'stable-updates'), (900, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages blueman depends on: ii bluez 4.99-2 ii dbus 1.6.8-1+deb7u3 ii gnome-icon-theme 3.4.0-2 ii libatk1.0-0 2.4.0-2 ii libbluetooth3 4.99-2 ii libc6 2.13-38+deb7u1 ii libcairo2 1.12.2-3 ii libfontconfig12.9.0-7.1 ii libfreetype6 2.4.9-1.1 ii libgdk-pixbuf2.0-02.26.1-1 ii libglib2.0-0 2.33.12+really2.32.4-5 ii libgtk2.0-0 2.24.10-2 ii libpango1.0-0 1.30.0-1 ii libpython2.7 2.7.3-6+deb7u2 ii librsvg2-common 2.36.1-2 ii libstartup-notification0 0.12-1 ii notify-osd [notification-daemon] 0.9.34-2 ii obex-data-server 0.4.5-1+b3 ii python2.7.3-4+deb7u1 ii python-dbus 1.1.1-1 ii python-gi 3.2.2-2 ii python-gtk2 2.24.0-3+b1 ii python-notify 0.1.1-3 ii python2.7 2.7.3-6+deb7u2 Versions of packages blueman recommends: ii libpulse-mainloop-glib0 4.0-6~bpo7+1 ii policykit-1 0.105-3 ii python-gconf 2.28.1+dfsg-1 blueman suggests no packages. -- no debconf information -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgpf3EHQPIIYw.pgp Description: PGP signature
Bug#754193: linux-image-3.2.0-4-amd64: reboot(2) called from a PID namespace shuts down a host
9-3 Versions of packages linux-image-3.2.0-4-amd64 recommends: pn firmware-linux-free none Versions of packages linux-image-3.2.0-4-amd64 suggests: pn debian-kernel-handbook none ii extlinux2:4.05+dfsg-6+deb7u1 pn linux-doc-3.2 none Versions of packages linux-image-3.2.0-4-amd64 is related to: pn firmware-atherosnone pn firmware-bnx2 none pn firmware-bnx2x none pn firmware-brcm80211 none pn firmware-intelwimax none pn firmware-ipw2x00none pn firmware-ivtv none pn firmware-iwlwifinone pn firmware-libertas none pn firmware-linux none pn firmware-linux-nonfree none pn firmware-myricomnone pn firmware-netxen none pn firmware-qlogic none pn firmware-ralink none pn firmware-realteknone pn xen-hypervisor none -- debconf information: linux-image-3.2.0-4-amd64/postinst/depmod-error-initrd-3.2.0-4-amd64: false linux-image-3.2.0-4-amd64/prerm/removing-running-kernel-3.2.0-4-amd64: true linux-image-3.2.0-4-amd64/postinst/ignoring-ramdisk: linux-image-3.2.0-4-amd64/postinst/missing-firmware-3.2.0-4-amd64: -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgpikoswdzdpD.pgp Description: PGP signature
Bug#754184: systemd: poweroff shuts down systemd-nspawn-ed container
It was 2014-07-08 wto 16:29, when Michael Biebl wrote: Am 08.07.2014 16:03, schrieb Michael Biebl: I can not reproduce this but I have to add that my host is running Debian sid with 204-14. The container was created as per your instructions. Have you bind-mounted /run or /dev/(shm) into the container? Actually, this is most likely a kernel issue. [...] Please update your kernel to the version from backports if you want to run systemd-nspawn and report back. Now I am running 3.12.9-1~bpo70+1 kernel and I cannot log into container. All I get is: login[96]: FAILED LOGIN (1) on '/dev/console' FOR 'root', System error Tomorrow I will try 3.14. -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgpF6uZbotDRy.pgp Description: PGP signature
Bug#753606: libsystemd-journal-dev: unable to install libsystemd-journal-dev=204-8~bpo70+1
Package: libsystemd-journal-dev Severity: grave Dear Maintainer, I've tried to install libsystemd-journal-dev=204-8~bpo70+1 from the wheezy-backports (libsystemd-id128-dev appears to have the same problem as described below). Suddenly apt decided it will remove the systemd package. It seems (to my debian-untrained eye) that the problem is in dependencies which state that libsystemd-journal-dev (and libsystemd-id128-dev too) replaces systemd 204-8 and my systemd=204-8~bpo70+1 appears to qualify for replacement. Please see below for the transcript. --8---cut here---start-8--- # apt-cache policy libsystemd-journal-dev libsystemd-journal-dev: Installed: (none) Candidate: 44-11+deb7u4 Version table: 204-8~bpo70+1 0 600 http://ftp.pl.debian.org/debian/ wheezy-backports/main amd64 Packages 44-11+deb7u4 0 900 http://ftp.pl.debian.org/debian/ wheezy/main amd64 Packages 900 http://security.debian.org/ wheezy/updates/main amd64 Packages # apt-get install libsystemd-journal-dev/wheezy-backports Reading package lists... Done Building dependency tree Reading state information... Done Selected version '204-8~bpo70+1' (Debian Backports:/wheezy-backports [amd64]) for 'libsystemd-journal-dev' Selected version '204-8~bpo70+1' (Debian Backports:/wheezy-backports [amd64]) for 'libsystemd-id128-dev' because of 'libsystemd-journal-dev' The following extra packages will be installed: libsystemd-id128-dev The following packages will be REMOVED: libpam-systemd systemd The following NEW packages will be installed: libsystemd-id128-dev libsystemd-journal-dev 0 upgraded, 2 newly installed, 2 to remove and 82 not upgraded. Need to get 70.4 kB of archives. After this operation, 5294 kB disk space will be freed. Do you want to continue [Y/n]? n # apt-cache show libsystemd-journal-dev/wheezy-backports Package: libsystemd-journal-dev Source: systemd Version: 204-8~bpo70+1 Installed-Size: 108 Maintainer: Debian systemd Maintainers pkg-systemd-maintain...@lists.alioth.debian.org Architecture: amd64 Replaces: systemd ( 204-8) Depends: libsystemd-journal0 (= 204-8~bpo70+1), libsystemd-id128-dev (= 204-8~bpo70+1) Breaks: systemd ( 204-8) Description-en: systemd journal utility library - development files The libsystemd-journal library provides an interface for the systemd journal service. . This package contains the development files Homepage: http://www.freedesktop.org/wiki/Software/systemd Description-md5: e80c34da97e3cfda38731839be115201 Section: libdevel Priority: optional Filename: pool/main/s/systemd/libsystemd-journal-dev_204-8~bpo70+1_amd64.deb Size: 46802 MD5sum: a125805271301fe14e246102eca9b1ab SHA1: 389e63a146fb52379fdb7cf57c81a403904e508c SHA256: 0279966b82607bb20127b4badf8739971ceabea5c5128ecf91e47d985717837d # dpkg --compare-versions '204-8~bpo70+1' '' '204-8'; echo $? 0 --8---cut here---end---8--- -- System Information: Debian Release: 7.5 APT prefers stable-updates APT policy: (990, 'stable-updates'), (900, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: armel Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- Łukasz Stelmach Samsung RD Institute Poland Samsung Electronics pgp9BxQPZbDFd.pgp Description: PGP signature
Bug#228112: indent: Adjustment of '*' in function declaration
Hi.
I've created a patch (attached) and sent it already to bug-indent
list. Unfortunately I haven't got any repsponse yet.
The patch solves 2/3 of the problem reported in this bug. It allows for
either:
function(type *variable)
function(type* variable)
but not
function(type * variable)
--
Łukasz Stelmach
Samsung RD Institute Poland
Samsung Electronics
From e0bee642b7ccdee2f6db251795c423f3e20494c3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C5=81ukasz=20Stelmach?= l.stelm...@samsung.com
Date: Fri, 7 Jun 2013 14:49:43 +0200
Subject: [PATCH] Customise '*' alignment in a pointer declaration
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Organization: Samsung RD Institute Poland
Signed-off-by: Łukasz Stelmach l.stelm...@samsung.com
---
doc/indent.texinfo | 10 ++
src/args.c |7 +++
src/handletoken.c | 14 +-
src/indent.h |1 +
4 files changed, 31 insertions(+), 1 deletion(-)
diff --git a/doc/indent.texinfo b/doc/indent.texinfo
index 08f35f6..e652d52 100644
--- a/doc/indent.texinfo
+++ b/doc/indent.texinfo
@@ -1958,6 +1958,16 @@ Use the original Berkeley coding style.@*
Do not read @file{.indent.pro} files.@*
@xref{Invoking indent}.
+@item -pal
+@itemx --pointer-align-left
+Put asterisks in pointer declarations on the left of spaces, next to
+types: ``char* p''.
+
+@item -par
+@itemx --pointer-align-left
+Put asterisks in pointer declarations on the righ of spaces, next to
+types: ``char *p''. This is the default behaviour.
+
@item -pcs
@itemx --space-after-procedure-calls
Insert a space between the name of the
diff --git a/src/args.c b/src/args.c
index f392cce..a0603c2 100644
--- a/src/args.c
+++ b/src/args.c
@@ -191,6 +191,7 @@ static int exp_ts = 0;
static int exp_ut = 0;
static int exp_v= 0;
static int exp_version = 0;
+static int exp_par = 0;
/**
* The following structure is controlled by command line parameters and
@@ -350,6 +351,8 @@ const pro_ty pro[] =
{bacc,PRO_BOOL, false, ON, settings.blanklines_around_conditional_compilation, exp_bacc},
{T, PRO_KEY,0, ONOFF_NA, 0, exp_T},
{ppi, PRO_INT,0, ONOFF_NA, settings.force_preproc_width, exp_ppi},
+{pal, PRO_BOOL,true, OFF, settings.pointer_align_right, exp_par},
+{par, PRO_BOOL,true, ON, settings.pointer_align_right, exp_par},
/* Signify end of structure. */
{0, PRO_IGN,0, ONOFF_NA, 0, 0}
};
@@ -469,6 +472,8 @@ const pro_ty pro[] =
{bacc,PRO_BOOL, false, ON, settings.blanklines_around_conditional_compilation, exp_bacc},
{T, PRO_KEY,0, ONOFF_NA, 0, exp_T},
{ppi, PRO_INT,0, ONOFF_NA, settings.force_preproc_width, exp_ppi},
+{pal, PRO_BOOL,true, OFF, settings.pointer_align_right, exp_par},
+{par, PRO_BOOL,true, ON, settings.pointer_align_right, exp_par},
/* Signify end of structure. */
{0, PRO_IGN,0, ONOFF_NA, 0, 0}
};
@@ -598,6 +603,8 @@ const long_option_conversion_ty option_conversions[] =
{berkeley,orig},
{Bill-Shannon,bs},
{preprocessor-indentation,ppi},
+{pointer-align-right, par},
+{pointer-align-left, pal},
/* Signify end of structure. */
{0, 0},
};
diff --git a/src/handletoken.c b/src/handletoken.c
index 7b0338c..806c693 100644
--- a/src/handletoken.c
+++ b/src/handletoken.c
@@ -575,11 +575,15 @@ static void handle_token_unary_op(
{
char * t_ptr;
-if (parser_state_tos-want_blank)
+if (parser_state_tos-want_blank
+ !(parser_state_tos-in_decl
+ !settings.pointer_align_right
+ *token == '*'))
{
set_buf_break (bb_unary_op, paren_target);
*(e_code++) = ' ';
*e_code = '\0'; /* null terminate code sect */
+parser_state_tos-want_blank = false;
}
else if (can_break)
{
@@ -628,6 +632,14 @@ static void handle_token_unary_op(
*(e_code++) = *t_ptr;
}
+if (parser_state_tos-want_blank
+!(parser_state_tos-in_decl
+ settings.pointer_align_right
+ *token == '*'))
+{
+set_buf_break
Bug#628761: bsdmainutils: make ncal print weeks in rows
Package: bsdmainutils Version: 8.0.13 Severity: wishlist According to bug #627167 cal won't be able to print weeks starting on Mondays. Then I'd like to ask for a switch to make ncal print weeks in rows. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bsdmainutils depends on: ii bsdutils 1:2.17.2-9 Basic utilities from 4.4BSD-Lite ii debianutils 3.4Miscellaneous utilities specific t ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-5 shared libraries for terminal hand bsdmainutils recommends no packages. Versions of packages bsdmainutils suggests: ii cpp 4:4.4.5-1 The GNU C preprocessor (cpp) pn vacation none (no description available) ii wamerican [wordlist] 6-3American English dictionary words ii wbritish [wordlist] 6-3British English dictionary words f ii whois 5.0.10 an intelligent whois client ii wpolish [wordlist]20100612-1 Polish dictionary words for /usr/s -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#609871: bsdmainutils: cal -m no longer makes week begin on Monday
Package: bsdmainutils Version: 8.0.13 Severity: normal File: /usr/bin/cal As long as I remember cal -m on all my GNU/Linux machines for the past 15 years, was the way to see a calendar for the current month with Monday as the first day of the week (check bsdmainutils-6.1.10ubuntu3). IMHO both Debian and Ubuntu bugs regarding -m option http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607960 https://bugs.launchpad.net/ubuntu/+source/bsdmainutils/+bug/693499 are pointless. To see February of 2022 one always had to type cal feb 2022 -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bsdmainutils depends on: ii bsdutils 1:2.17.2-3.3 Basic utilities from 4.4BSD-Lite ii debianutils 3.4Miscellaneous utilities specific t ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-4 shared libraries for terminal hand bsdmainutils recommends no packages. Versions of packages bsdmainutils suggests: ii cpp 4:4.4.5-1 The GNU C preprocessor (cpp) pn vacation none (no description available) ii wamerican [wordlist] 6-3American English dictionary words ii wbritish [wordlist] 6-3British English dictionary words f ii whois 5.0.10 an intelligent whois client ii wpolish [wordlist]20100612-1 Polish dictionary words for /usr/s -- no debconf information -- Miłego dnia, Łukasz Stelmach -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#529582: texlive-xetex: fontspec breaks em-dash
Hilmar Preusse hill...@web.de writes: Can you still reproduce the problem in TL 2009, I can't (AFAICT). Quotes work fine and --- becomes a single dash too but it doesn't look exactly the same as \pauza. It is much thinner and has bigger spacing around it. The smaller spacing of \pauza is defined in polski.sty but I can't find out why --- is much thinner (invisible when A4 fits 20 screen). -- Miłego dnia, Łukasz Stelmach -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575920: reportbug: ask for the version of the package to be reported as buggy
Sandro Tosi mo...@debian.org writes: 2010/3/30 Łukasz Stelmach lukasz.stelm...@iem.pw.edu.pl: Package: reportbug Version: 4.10.2 Severity: wishlist Yesterday I managed to fix a problem with nvidia-glx package. I installed the version from the unstable repository. The I filed a bug report about, as I was hoping, the older buggy version. Because and what version would that be? how can reportbug select the correct version? how can reportbug know the /older/ version? or you may mean the two-versions-ago, or any other variation. First write your reply then maybe read what it is about? reportbug generates a template with a fat sing Please type etc. and I am not too interested in details of Debian bug reporting process I don't even look above that line. I should have. The bug was filed against the unstable version which wasn't my intention nad got closed immediatelly. if you managed to fix a bug in a version that's already superseded by the unstable one, then you should not in the first place report the bug. a fix that's already in unstable will (sooner or later) transit to testing and then to stable so there's nothing to fix. Such a report might make this happen sooner which might be... convenient for other, maybe less skilled, users who (they should die and go to hell) happen to use Debian testing. You know, even noobs sometimes use google which quite oftne points to bugreports. How about having one with a workaround? I wish report bug explicitly asked a question File the report against version X.Y.Z [Y|n]: Since you know what version you want to file the bugs against, you can use the option reportbug already provides: -V PKGVERSION, --package-version=PKGVERSION specify the version number for the package Great option, I'd like to have yet another one. Dou you like Perl? I do. In most cases users hit [Enter]. It'd be closer to other bug tracking systems wher users choose on their own the version to be reported as buggy. this is not an argument: using debian BTS you should stick to its peculiarities, like this one. Thank gods there are people who don't alway to stick to peculiarities and we don't need to program computers with a magnetised needle. If it's too hard for you to name things properly I ask for a change in the user's interface. Making the bugreporting interface comfortable is the first step to get better reports. That said, I'm closing this report. Wonderful feeling isn't it? -- Miłego dnia, Łukasz Stelmach -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575826: closed by Julien Cristau jcris...@debian.org (Re: Bug#575826: nvidia-glx: 173.14.09 doesn't work on testing anymore)
ow...@bugs.debian.org (Debian Bug Tracking System) writes: The previous version of nvidia-glx (I've installed 190.53-2 on my own) doesn't work with xorg-xserver 1:7.5+5. I've got messages about resVgaShared missing symbol. Then don't file a bug against the working version... Yeah, sure! I sit half an hour to figure out how to bring my system back to life (and posibly keep it that way after next time you forget about dependencies) just to hear from you that I should break it again before filing a bug report. Am I the only insane here? -- Miłego dnia, Łukasz Stelmach -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575920: reportbug: ask for the version of the package to be reported as buggy
Package: reportbug Version: 4.10.2 Severity: wishlist Yesterday I managed to fix a problem with nvidia-glx package. I installed the version from the unstable repository. The I filed a bug report about, as I was hoping, the older buggy version. Because reportbug generates a template with a fat sing Please type etc. and I am not too interested in details of Debian bug reporting process I don't even look above that line. I should have. The bug was filed against the unstable version which wasn't my intention nad got closed immediatelly. I wish report bug explicitly asked a question File the report against version X.Y.Z [Y|n]: In most cases users hit [Enter]. It'd be closer to other bug tracking systems wher users choose on their own the version to be reported as buggy. -- Package-specific info: ** Environment settings: INTERFACE=text ** /home/steelman/.reportbugrc: reportbug_version 3.39 mode standard ui text realname Łukasz Stelmach email lukasz.stelm...@iem.pw.edu.pl -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages reportbug depends on: ii apt 0.7.25.3 Advanced front-end for dpkg ii python2.5.4-9An interactive high-level object-o ii python-reportbug 4.10.2 Python modules for interacting wit reportbug recommends no packages. Versions of packages reportbug suggests: pn debconf-utilsnone (no description available) pn debsums none (no description available) pn dlocate none (no description available) ii emacs23-bin-common 23.1+1-5The GNU Emacs editor's shared, arc ii exim44.71-3 metapackage to ease Exim MTA (v4) ii exim4-daemon-light [ 4.71-3 lightweight Exim MTA (v4) daemon ii file 5.04-1 Determines file type using magic ii gnupg1.4.10-2GNU privacy guard - a free PGP rep ii python-gtk2 2.16.0-2Python bindings for the GTK+ widge ii python-gtkspell 2.25.3-4.1+b3 Python bindings for the GtkSpell l pn python-urwid none (no description available) ii python-vte 1:0.22.5-3 Python bindings for the VTE widget ii xdg-utils1.0.2+cvs20100307-1 desktop integration utilities from -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#575826: nvidia-glx: 173.14.09 doesn't work on testing anymore
Package: nvidia-glx Version: 190.53-2 Severity: grave Justification: renders package unusable The previous version of nvidia-glx (I've installed 190.53-2 on my own) doesn't work with xorg-xserver 1:7.5+5. I've got messages about resVgaShared missing symbol. -- Package-specific info: uname -r: Linux dasa3 2.6.32-trunk-amd64 #1 SMP Sun Jan 10 22:40:40 UTC 2010 x86_64 GNU/Linux /proc/version: Linux version 2.6.32-trunk-amd64 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Sun Jan 10 22:40:40 UTC 2010 /proc/driver/nvidia/version: 00:05.0 VGA compatible controller: nVidia Corporation C51PV [GeForce 6150] (rev a2) -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages nvidia-glx depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libx11-6 2:1.3.3-2 X11 client-side library ii libxext6 2:1.1.1-3 X11 miscellaneous extension librar ii nvidia-kernel-2.6.32-t 190.53-2+2.6.32-5 NVIDIA binary kernel module for Li ii x11-common 1:7.5+5 X Window System (X.Org) infrastruc nvidia-glx recommends no packages. Versions of packages nvidia-glx suggests: ii nvidia-kernel-source 190.53-2 NVIDIA binary kernel module source ii nvidia-settings 190.53-1 Tool for configuring the NVIDIA gr -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
