Bug#1017976: emacsen-common: Segmentation fault when upgrading emacs to 28.1+1-2
Package: emacsen-common Version: 3.0.4 Severity: important X-Debbugs-Cc: debb...@chiraag.me Dear Maintainer, When upgrading emacs to 28.1+1-2 from 27.1 (previous version) in sid/experimental, emacsen-common throws a segmentation fault when configuring: Fatal error 11: Segmentation fault Backtrace: emacs(+0x153373)[0x56339f61e373] emacs(+0x48827)[0x56339f513827] emacs(+0x48cf0)[0x56339f513cf0] emacs(+0x1516d8)[0x56339f61c6d8] emacs(+0x151759)[0x56339f61c759] /lib/x86_64-linux-gnu/libc.so.6(+0x3daa0)[0x7f57dd23daa0] emacs(+0x193eb4)[0x56339f65eeb4] emacs(+0x199752)[0x56339f664752] emacs(+0x1b7e5d)[0x56339f682e5d] emacs(+0x1b7f6f)[0x56339f682f6f] emacs(+0x1de858)[0x56339f6a9858] emacs(+0x1df220)[0x56339f6aa220] emacs(+0x1e29bb)[0x56339f6ad9bb] emacs(+0x1e35ba)[0x56339f6ae5ba] emacs(+0x1b7af6)[0x56339f682af6] emacs(+0x1b7d25)[0x56339f682d25] emacs(+0x1b7f6f)[0x56339f682f6f] emacs(+0x1de858)[0x56339f6a9858] emacs(+0x1df220)[0x56339f6aa220] emacs(+0x1e29bb)[0x56339f6ad9bb] emacs(+0x1e35ba)[0x56339f6ae5ba] emacs(+0x1b7af6)[0x56339f682af6] emacs(+0x1b7d25)[0x56339f682d25] emacs(+0x1b7f6f)[0x56339f682f6f] emacs(+0x1de858)[0x56339f6a9858] emacs(+0x1df220)[0x56339f6aa220] emacs(+0x1e29bb)[0x56339f6ad9bb] emacs(+0x1e35ba)[0x56339f6ae5ba] emacs(+0x1b7af6)[0x56339f682af6] emacs(+0x1b7d25)[0x56339f682d25] emacs(+0x1b7f6f)[0x56339f682f6f] emacs(+0x1de858)[0x56339f6a9858] emacs(+0x1df220)[0x56339f6aa220] emacs(+0x1e29bb)[0x56339f6ad9bb] emacs(+0x1e35ba)[0x56339f6ae5ba] emacs(+0x1b7af6)[0x56339f682af6] emacs(+0x1b7d25)[0x56339f682d25] emacs(+0x1b7f6f)[0x56339f682f6f] emacs(+0x1de858)[0x56339f6a9858] emacs(+0x1df220)[0x56339f6aa220] emacs(+0x1e29bb)[0x56339f6ad9bb] ... Segmentation fault -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.19.0-trunk-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=kn_IN.UTF8, LC_CTYPE=kn_IN.UTF8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
Bug#997844: grub2-common: GRUB_THEME setting broken when used with encrypted disks
Package: grub2-common
Version: 2.04-20
Severity: normal
X-Debbugs-Cc: debb...@chiraag.me
Dear Maintainer,
My setup is as follows. I have 2 storage disks, one SATA HDD and one M.2 NVME
SSD. Both disks are encrypted, and the layout is as follows:
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:00 1.8T 0 disk
└─sda18:10 1.8T 0 part
└─sda1_crypt 254:30 1.8T 0 crypt
└─Crypto--Data-Home 254:40 1.8T 0 lvm /home
nvme0n1 259:00 465.8G 0 disk
├─nvme0n1p1 259:10 476M 0 part /boot/efi
├─nvme0n1p2 259:20 477M 0 part /boot
└─nvme0n1p3 259:30 464.8G 0 part
└─nvme0n1p3_crypt 254:00 464.8G 0 crypt
├─Crypto-Root 254:10 425.6G 0 lvm /
└─Crypto-Swap 254:20 29.8G 0 lvm [SWAP]
That is, the NVME SSD is split into 3 partitions: one for /boot/efi, one for
/boot, and one encrypted partition which provides both / and swap through LVM
partitions. The HDD is quite simple — just one giant encrypted partition with a
single LVM partition inside (mainly for consistency). That's the setup.
Okay, so here's the issue. I don't normally view the GRUB menu (I have a hidden
timeout and I normally go straight to my plymouth splash screen), but I'd like
it to look nice if I ever have to open it up. Accordingly, I set a theme by
putting GRUB_THEME="/usr/share/grub/themes/starfield/theme.txt" in
/etc/default/grub. I even get the appropriate output when I run sudo
update-grub (also reflected by the /boot/grub/grub.cfg attached by reportbug):
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/starfield/theme.txt
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-5.14.0-3-amd64
Found initrd image: /boot/initrd.img-5.14.0-3-amd64
Found linux image: /boot/vmlinuz-5.14.0-2-amd64
Found initrd image: /boot/initrd.img-5.14.0-2-amd64
Adding boot menu entry for EFI firmware configuration
done
However, the menu still takes on the default look (blue menu, no background
image, etc). What I realized is that GRUB doesn't seem to copy the background
image into /boot/grub/, and since the disk isn't yet decrypted, it can't access
the background image at the place it's looking for it.
This feels like a bug because there is every indication (including from
update-grub2) that a theme will be used, but then the theme silently fails.
I'd be happy to answer any questions or provide further info if required.
Sincerely,
Chiraag
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/mapper/Crypto-Root / ext4 rw,relatime,errors=remount-ro 0 0
/dev/nvme0n1p2 /boot ext4 rw,relatime 0 0
/dev/nvme0n1p1 /boot/efi vfat
rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro
0 0
/dev/mapper/Crypto--Data-Home /home ext4 rw,relatime 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod lvm
insmod ext2
set
root='lvmid/spfV9e-Y509-RNhq-E4Gw-RILD-Q1Hf-qMPadi/9VUvbi-VvjU-eIc9-49fF-Sq33-7Vm9-mEi93Y'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
--hint='lvmid/spfV9e-Y509-RNhq-E4Gw-RILD-Q1Hf-qMPadi/9VUvbi-VvjU-eIc9-49fF-Sq33-7Vm9-mEi93Y'
1784b59b-9d7b-4a59-bb89-6a124262500e
else
search --no-floppy --fs-uuid --set=root 1784b59b-9d7b-4a59-bb89-6a124262500e
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=kn_IN
insmod gettext
fi
terminal_output gfxterm
insmod lvm
insmod ext2
set
Bug#972286: coreutils: Crash when using globs on a path with non-latin characters
15/10/20 17:29 ನಲ್ಲಿ, Michael Stone ಬರೆದರು:
>
> On Thu, Oct 15, 2020 at 04:28:35PM -0400, you wrote:
> >Steps to reproduce:
> >
> >1. mkdir ~/ಇಳಿಕೆಗಳು
> >2. touch ~/ಇಳಿಕೆಗಳು/{a,b}.txt
> >3. ls ~/ಇಳಿಕೆಗಳು/*.txt crashes immediately
> >
> >By contrast:
> >
> >1. cd ~/ಇಳಿಕೆಗಳು/ && ls *.txt succeeds
> >2. ls ಇಳಿಕೆಗಳು/*.txt succeeds
> >
> >Similarly, `cp ~/ಇಳಿಕೆಗಳು/*.txt .` crashes, but `cp ಇಳಿಕೆಗಳು/*.txt .` works,
> >as does `cd ಇಳಿಕೆಗಳು && cp *.txt ~`.
> >
> >Please let me know if you need more information.
>
> coreutils doesn't have anything to do with expanding a shell wildcard,
> the bug needs to be assigned to whatever shell you're using.
Got it, I'll submit this to bash (verified that it's a shell problem by testing
with a different shell).
publickey - debbugs@chiraag.me.asc.pgp
Description: application/pgp-key
signature.asc
Description: OpenPGP digital signature
Bug#972286: Clarification
It seems that the key part is including the ~ character along with non-latin
elements of the path.
The following work:
1. ls ${HOME}/ಇಳಿಕೆಗಳು/*.txt
2. ls /home/$(whoami)/ಇಳಿಕೆಗಳು/*.txt
3. ls ~/.config/*rc
While `ls ~/ಇಳಿಕೆಗಳು/*.txt` does not.
- Chiraag
--
ಚಿರಾಗ್ ನಟರಾಜ್
Pronouns: he/him/his
publickey - debbugs@chiraag.me.asc.pgp
Description: application/pgp-key
signature.asc
Description: OpenPGP digital signature
Bug#972286: coreutils: Crash when using globs on a path with non-latin characters
Package: coreutils
Version: 8.32-4+b1
Severity: important
Tags: l10n
X-Debbugs-Cc: debb...@chiraag.me
Dear Maintainer,
Steps to reproduce:
1. mkdir ~/ಇಳಿಕೆಗಳು
2. touch ~/ಇಳಿಕೆಗಳು/{a,b}.txt
3. ls ~/ಇಳಿಕೆಗಳು/*.txt crashes immediately
By contrast:
1. cd ~/ಇಳಿಕೆಗಳು/ && ls *.txt succeeds
2. ls ಇಳಿಕೆಗಳು/*.txt succeeds
Similarly, `cp ~/ಇಳಿಕೆಗಳು/*.txt .` crashes, but `cp ಇಳಿಕೆಗಳು/*.txt .` works, as
does `cd ಇಳಿಕೆಗಳು && cp *.txt ~`.
Please let me know if you need more information.
- Chiraag
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=kn_IN.UTF-8, LC_CTYPE=kn_IN.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 coreutils depends on:
ii libacl1 2.2.53-8
ii libattr1 1:2.4.48-5
ii libc62.31-4
ii libgmp10 2:6.2.0+dfsg-6
ii libselinux1 3.1-2+b1
coreutils recommends no packages.
coreutils suggests no packages.
-- no debconf information
Bug#970869: openvpn: Incorrect handling of multiple instances of template service
Package: openvpn Version: 2.5~beta3-1 Severity: important X-Debbugs-Cc: debb...@chiraag.me Dear Maintainer, I happened to run into an interesting issue and I'm not entirely sure if the problem is in openvpn, openvpn-systemd-resolved, or systemd-resolved. 1. I have several configuration files in /etc/openvpn, say A.conf and B.conf. 2. I run sudo systemctl start openvpn@A and note that the tunnel is established, DNS queries don't leak, etc. Everything's good. 3. I then run sudo systemctl start openvpn@B and note that a new tunnel is established and DNS queries are (at the very least) _also_ routed to the new DNS server. Everything's still good (I'm not sure if DNS queries are *also* routed to the first VPN server's DNS server due to both having dhcp-option DOMAIN-ROUTE ., but that's irrelevant for my specific use-case and irrelevant to this bug). 4. I then disconnect from B by running sudo systemctl stop openvpn@B and note that the first tunnel is still established (good!), but all traffic seems to be directed to my main network interface instead (bad!). This can be verified by going to e.g. https://whatismyipaddress.com and noticing that your ISP's IP address is the one showing there rather than the IP address assigned by your VPN provider. I would have expected the first tunnel to take over the connection, especially since resolvectl status still seemed to indicate that everything was set correctly on the DNS end (correct domain routing, etc) and systemctl status openvpn@A seemed to show that the VPN is still connected. Sincerely, Chiraag -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=kn_IN.UTF-8, LC_CTYPE=kn_IN.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 openvpn depends on: ii debconf [debconf-2.0] 1.5.74 ii iproute2 5.8.0-1 ii libc6 2.31-3 ii liblz4-1 1.9.2-2 ii liblzo2-2 2.10-2 ii libpam0g 1.3.1-5 ii libpkcs11-helper1 1.26-1+b1 ii libssl1.1 1.1.1g-1 ii libsystemd0246.6-1 ii lsb-base 11.1.0 Versions of packages openvpn recommends: pn easy-rsa Versions of packages openvpn suggests: hi openssl 1.1.1g-1 ii openvpn-systemd-resolved 1.3.0-3 pn resolvconf -- Configuration Files: /etc/openvpn/update-resolv-conf [Errno 13] Permission denied: '/etc/openvpn/update-resolv-conf' -- debconf information excluded
Bug#968569: cryptsetup-suspend: Set OOMScoreAdjust to -1000 to disable OOM killing for the modified systemd-suspend service
Package: cryptsetup-suspend Version: 2:2.3.3-3+exp1 Severity: wishlist X-Debbugs-Cc: debb...@chiraag.me Dear Maintainer, The OOMScoreAdjust for the modified systemd-suspend.service is -999. The minimum possible is -1000, which should competely disable the OOM Killer. Is there a reason -1000 wasn't chosen? -- Package-specific info: -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=kn_IN.UTF-8, LC_CTYPE=kn_IN.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 cryptsetup-suspend depends on: ii cryptsetup-initramfs 2:2.3.3-3+exp1 ii libc6 2.31-3 ii libcryptsetup12 2:2.3.3-3+exp1 ii systemd 246.1-1 cryptsetup-suspend recommends no packages. cryptsetup-suspend suggests no packages. -- no debconf information
Bug#928915: Full log unavailable with -e or -x
Hmm, it seems there's been a change in behavior? Before I upgraded, I could access the full log with -xe, but it seems that now -e implies -n1000? So I guess this isn't explicitly an issue, but it was a surprise after I upgraded. Sincerely, Chiraag -- ಚಿರಾಗ್ ನಟರಾಜ್ Graduate Student at Brown University Email: chiraag.nata...@gmail.com Phone: 610-350-6329 Website: http://chiraag.nataraj.us signature.asc Description: PGP signature
Bug#928915: systemd: Full log unavailable with -e or -x
Package: systemd
Version: 242-1
Severity: normal
Dear Maintainer,
Different invocations of journalctl seem to display different amounts of the
log.
$ sudo journalctl -xe
-- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:16:32
EDT. --
ಮೇ 12 20:44:29 chiraag env[8395]:
{"name":"log","hostname":"chiraag","pid":203,"level":30,"msg":"GET
https://textsecure-service.whispersystems.org/
$ sudo journalctl -x
-- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:16:32
EDT. --
ಮೇ 12 20:44:29 chiraag env[8395]:
{"name":"log","hostname":"chiraag","pid":203,"level":30,"msg":"GET
https://textsecure-service.whispersystems.org/
$ sudo journalctl -e
-- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:16:32
EDT. --
ಮೇ 12 20:44:29 chiraag env[8395]:
{"name":"log","hostname":"chiraag","pid":203,"level":30,"msg":"GET
https://textsecure-service.whispersystems.org/
$ sudo journalctl
-- Logs begin at Sun 2019-05-12 20:37:51 EDT, end at Sun 2019-05-12 21:17:17
EDT. --
ಮೇ 12 20:37:51 chiraag kernel: microcode: microcode updated early to revision
0x9a, date = 2018-07-16
I included the first line only, but it should get the point across. I scrolled
back up to the top with the invocations which include -e, so that's not the
issue. Additionally, this seems to not be an issue if I use --unit to filter by
regexp.
Sincerely,
Chiraag
-- Package-specific info:
-- System Information:
Debian Release: 10.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.0.2-chiraag (SMP w/8 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=kn_IN.UTF-8, LC_CTYPE=kn_IN.UTF-8 (charmap=UTF-8),
LANGUAGE=kn_IN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages systemd depends on:
ii adduser 3.118
ii libacl1 2.2.53-4
ii libapparmor1 2.13.2-10
ii libaudit11:2.8.4-3
ii libblkid12.33.1-0.1
ii libc62.28-10
ii libcap2 1:2.25-2
ii libcryptsetup12 2:2.2.0~rc0-1
ii libgcrypt20 1.8.4-5
ii libgnutls30 3.6.7-2
ii libgpg-error01.36-1
ii libidn2-02.0.5-1
ii libip4tc01.8.2-4
ii libkmod2 26-1
ii liblz4-1 1.8.3-1
ii liblzma5 5.2.4-1
ii libmount12.33.1-0.1
ii libpam0g 1.3.1-5
ii libpcre2-8-0 10.32-5
ii libseccomp2 2.3.3-4
ii libselinux1 2.9-1
ii libsystemd0 242-1
ii mount2.33.1-0.1
ii util-linux 2.33.1-0.1
Versions of packages systemd recommends:
ii dbus1.13.8-1
ii libpam-systemd 242-1
Versions of packages systemd suggests:
ii policykit-10.116-1
pn systemd-container
Versions of packages systemd is related to:
pn dracut
ii initramfs-tools 0.133
ii udev 242-1
-- Configuration Files:
/etc/systemd/resolved.conf changed [not included]
-- no debconf information
Bug#928914: Fix for #898892 breaks normal usage
Never mind, I'm an idiot. The name of the unit was boinc-client.service. Sincerely, Chiraag signature.asc Description: PGP signature
Bug#928914: systemd: Fix for #898892 breaks normal usage
Package: systemd Version: 242-1 Severity: normal Dear Maintainer, It seems the fix for #898892 renders bare unit names unusable. Example: $ sudo journalctl --unit boinc -- No entries -- $ sudo journalctl --unit boinc* ಮೇ 12 20:39:36 chiraag systemd[1]: Started Berkeley Open Infrastructure Network Computing Client. ಮೇ 12 20:39:38 chiraag boinc[1405]: 12-May-2019 20:39:38 [---] Starting BOINC client version 7.14.2 for x86_64-pc-linux-gnu ಮೇ 12 20:39:38 chiraag boinc[1405]: 12-May-2019 20:39:38 [---] log flags: file_xfer ಮೇ 12 20:39:38 chiraag boinc[1405]: 12-May-2019 20:39:38 [---] Libraries: libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+l ಮೇ 12 20:39:38 chiraag boinc[1405]: 12-May-2019 20:39:38 [---] Data directory: /var/lib/boinc-client That is, in order for me to view the logs of boinc.service, I need to pass boinc* as the argument to --unit (--unit boinc.service gives me the same result as --unit boinc). Sincerely, Chiraag -- Package-specific info: -- System Information: Debian Release: 10.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.0.2-chiraag (SMP w/8 CPU cores; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=kn_IN.UTF-8, LC_CTYPE=kn_IN.UTF-8 (charmap=UTF-8), LANGUAGE=kn_IN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages systemd depends on: ii adduser 3.118 ii libacl1 2.2.53-4 ii libapparmor1 2.13.2-10 ii libaudit11:2.8.4-3 ii libblkid12.33.1-0.1 ii libc62.28-10 ii libcap2 1:2.25-2 ii libcryptsetup12 2:2.2.0~rc0-1 ii libgcrypt20 1.8.4-5 ii libgnutls30 3.6.7-2 ii libgpg-error01.36-1 ii libidn2-02.0.5-1 ii libip4tc01.8.2-4 ii libkmod2 26-1 ii liblz4-1 1.8.3-1 ii liblzma5 5.2.4-1 ii libmount12.33.1-0.1 ii libpam0g 1.3.1-5 ii libpcre2-8-0 10.32-5 ii libseccomp2 2.3.3-4 ii libselinux1 2.9-1 ii libsystemd0 242-1 ii mount2.33.1-0.1 ii util-linux 2.33.1-0.1 Versions of packages systemd recommends: ii dbus1.13.8-1 ii libpam-systemd 242-1 Versions of packages systemd suggests: ii policykit-10.116-1 pn systemd-container Versions of packages systemd is related to: pn dracut ii initramfs-tools 0.133 ii udev 242-1 -- Configuration Files: /etc/systemd/resolved.conf changed [not included] -- no debconf information
Bug#918532: Acknowledgement (emacs: Daemon mode does not apply font preferences)
Never mind, fixed it using code from https://stackoverflow.com/questions/33074370/how-can-i-use-a-different-ttf-fonts-for-certain-utf-8-characters-in-emacs. Basically, the idea is to hook into the 'after-make-frame-functions hook. I found that I also had to manually call the function so that just directly running emacs would still apply the font preferences. Seems like this is a fairly long-standing issue that people have just worked around for a while... Anyway, feel free to close this. Sincerely, Chiraag -- ಚಿರಾಗ್ ನಟರಾಜ್ Graduate Student at Brown University Email: chiraag.nata...@gmail.com Phone: 610-350-6329 Website: http://chiraag.nataraj.us On 07/01/19 07:57, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 918532: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918532. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Rob Browning > > If you wish to submit further information on this problem, please > send it to 918...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 918532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918532 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems signature.asc Description: PGP signature
Bug#918532: emacs: Daemon mode does not apply font preferences
Package: emacs Version: 1:26.1+1-3 Severity: normal Tags: l10n Dear Maintainer, Here are the steps to reproduce the problem: 1. Install fonts-knda so that all three available fonts are installed. 2. Note that, by default, emacs (at least my emacs) prefers to use Gubbi to render the font. This is an issue because specific characters are rendered badly (a bug in its own right, but not something I'm overly concerned with at the moment). 3. Try to fix this by inserting `(set-fontset-font "fontset-default" (cons (decode-char 'ucs #x0c80) (decode-char 'ucs #x0cff)) "Lohit Kannada")` in your .emacs file. 4. Run `emacs` and note that the font preference is (correctly) applied. 5. Run `emacs --daemon` and note that the font preference is not applied. 6. After starting the daemon, if I go to my .emacs and evaluate that line manually, the preference is applied. This occurs with both emacs-lucid and emacs-gtk. If there is some more debugging info I can provide, please let me know. Sincerely, Chiraag -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.5-chiraag (SMP w/8 CPU cores; PREEMPT) Locale: LANG=kn_IN.UTF-8, LC_CTYPE=kn_IN.UTF-8 (charmap=UTF-8), LANGUAGE=kn_IN.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages emacs depends on: ii emacs-lucid 1:26.1+1-3 emacs recommends no packages. emacs suggests no packages. -- no debconf information
Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2
> No, I tried lightdm lxdm, they have same problem, > I tried gdm3, but can not login, do not why, the screen just become to > blank/black. > Any idea, how to debug? Can you try creating a new user and trying to log in as that user? There might be something going on with your specific user configuration (do you have any user units in ~/.config/systemd/user?). - Chiraag -- ಚಿರಾಗ್ ನಟರಾಜ್ Graduate Student at Brown University Email: chiraag.nata...@gmail.com Phone: 610-350-6329 Website: http://chiraag.nataraj.us signature.asc Description: PGP signature
Bug#894273: policykit-1-gnome: polkit-gnome-authentication-agent-1 fails to start when hidepid=2
Huh, thanks - I didn't think to look at polkit itself. Sorry for the dup. So it seems polkit itself is effectively completely broken when using hidepid, and there is no way to fix it without defeating the _purpose_ of hidepid (granting my user the privileges to see the full /proc tree basically disables hidepid, although it may still be useful for hiding /proc from _other_ users, e.g. ones that run various daemons...?). As I don't really use polkit much, I don't think I'll be doing that, but I think we should at least list this somewhere in the readme or package description for policykit-1 so that affected users know about the current solution (this is more important now that systemd uses polkit for authorization and a broken polkit means a broken systemd, at least in terms of interactive authorization). Sincerely, Chiraag -- ಚಿರಾಗ್ ನಟರಾಜ್ Graduate Student at Brown University Email: chiraag.nata...@gmail.com Phone: 610-350-6329 Website: http://chiraag.nataraj.us signature.asc Description: PGP signature
Bug#890299: Comparison for Gubbi versus Lohit Kannada
The character is the same for both (ಚ್), but is rendered very differently depending on which font is being used. I should note that this only seems to be a problem in Emacs - for example, the font renders perfectly well in firefox. wrong.png is rendered using Gubbi. right.png is rendered using Lohit Kannada. -- ಚಿರಾಗ್ ನಟರಾಜ್ Graduate Student at Brown University Email: chiraag.nata...@gmail.com Phone: 610-350-6329 Website: http://chiraag.nataraj.us signature.asc Description: PGP signature
Bug#890299: segfault log attached
The output when emacs segfaults is attached. Please let me know if you need more information. -- ಚಿರಾಗ್ ನಟರಾಜ್ Graduate Student at Brown University Email: chiraag.nata...@gmail.com Phone: 610-350-6329 Website: http://chiraag.nataraj.us Fatal error 11: Segmentation fault Backtrace: emacs25[0x502a5e] emacs25[0x4e8fa9] emacs25[0x5011ae] emacs25[0x501368] emacs25[0x5013f5] /lib/x86_64-linux-gnu/libpthread.so.0(+0x11f50)[0x7fc4312d2f50] /usr/lib/x86_64-linux-gnu/libotf.so.0(+0xea95)[0x7fc431c81a95] /usr/lib/x86_64-linux-gnu/libotf.so.0(+0xfe64)[0x7fc431c82e64] /usr/lib/x86_64-linux-gnu/libotf.so.0(OTF_drive_gpos_with_log+0x2a)[0x7fc431c84a2a] emacs25[0x5bad66] /usr/lib/x86_64-linux-gnu/libm17n-flt.so.0(+0x24f2)[0x7fc43183d4f2] /usr/lib/x86_64-linux-gnu/libm17n-flt.so.0(+0x5f67)[0x7fc431840f67] /usr/lib/x86_64-linux-gnu/libm17n-flt.so.0(+0x5f67)[0x7fc431840f67] /usr/lib/x86_64-linux-gnu/libm17n-flt.so.0(+0x5b53)[0x7fc431840b53] /usr/lib/x86_64-linux-gnu/libm17n-flt.so.0(+0x5f67)[0x7fc431840f67] /usr/lib/x86_64-linux-gnu/libm17n-flt.so.0(+0x6b98)[0x7fc431841b98] /usr/lib/x86_64-linux-gnu/libm17n-flt.so.0(mflt_run+0x2f1)[0x7fc431842e51] emacs25[0x5bbcdd] emacs25[0x5bf64e] emacs25[0x56b9b9] emacs25[0x55c0e5] emacs25[0x590983] emacs25[0x55e3ad] emacs25[0x55befb] emacs25[0x55b6a6] emacs25[0x42b00c] emacs25[0x438c3c] emacs25[0x5af9c6] emacs25[0x5b388c] emacs25[0x4423c4] emacs25[0x441fa8] emacs25[0x440475] emacs25[0x442702] emacs25[0x444e35] emacs25[0x44bfa1] emacs25[0x44ee0e] emacs25[0x42f4d8] emacs25[0x453626] emacs25[0x45392f] emacs25[0x453a9c] emacs25[0x5531be] ... Segmentation fault signature.asc Description: PGP signature
Bug#890211: [Pkg-fonts-devel] Bug#890211: fonts-noto-hinted: Certain font characters crash Emacs 25
Hi Jonas, On Mon, Feb 12, 2018 at 09:53:11AM +0100, Jonas Smedegaard wrote: > Hi Chiraag, > > Quoting Chiraag Nataraj (2018-02-12 02:00:06) > > I went to open mpc in Emacs, and my artists (and song titles) are in > > multiple languages, including Kannada (the font for which I found this > > problem). A very specific character (ಕು) caused Emacs to crash. This > > was reproducible multiple times using both the GTK+ and Lucid builds > > of Emacs 25. > > > > I uninstalled the package, which prevented the crash (that is, other > > fonts - e.g. the ones provided by fonts-knda - do not have this > > problem and do not cause Emacs to crash). > > > > I can provide more information if needed. > > Interesting! I will make sure to pass this upstream to the developers > of Noto. Great, thanks! > > Please also file a separate bugreport against emacs, as I am sure they > would love to know about the crashing bug on their side (and I don't use > emacs myself so cannot sensibly report that on my own). > Yup, I'll file a report with them as well. > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private - Chiraag -- ಚಿರಾಗ್ ನಟರಾಜ್ Graduate Student at Brown University Email: chiraag.nata...@gmail.com Phone: 610-350-6329 Website: http://chiraag.nataraj.us signature.asc Description: PGP signature
Bug#817960: libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6
On Sat, Mar 12, 2016 at 04:50:17PM +0100, Aurelien Jarno wrote: > Thanks for your screenshot, it definitely helps. The symbol > h_errno@GLIBC_PRIVATE has been renamed into __h_errno@GLIBC_PRIVATE in > glibc 2.22. > > Normally if you use both libpthread.so.0 and libc.so.6 from glibc 2.21 > and glibc 2.22 everything should work. In your case it seems after the > upgrade you end up with libc.so.6 from glibc 2.21 (instead of 2.22) > while libpthread.so.0 is from glibc 2.22. It might be you have a copy if > libc.so.6 somewhere in the locations ld.so is search for. > > Could you therefore please send me the output of "ldd /bin/ls" before > upgrading your system? That should give something like that: > > linux-vdso.so.1 (0x7ffe1013f000) > libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 > (0x7f836df6f000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f836dbcb000) > libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 > (0x7f836d95a000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f836d756000) > /lib64/ld-linux-x86-64.so.2 (0x562bc2437000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x7f836d539000) > > You should check if the libc.so.6 which is used is the one from > /lib/x86_64-linux-gnu or if another one is used. Looks like that fixed it! Thank you so much! - Chiraag signature.asc Description: PGP signature
Bug#817960: libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6
On Sat, Mar 12, 2016 at 04:50:17PM +0100, Aurelien Jarno wrote: > Thanks for your screenshot, it definitely helps. The symbol > h_errno@GLIBC_PRIVATE has been renamed into __h_errno@GLIBC_PRIVATE in > glibc 2.22. > > Normally if you use both libpthread.so.0 and libc.so.6 from glibc 2.21 > and glibc 2.22 everything should work. In your case it seems after the > upgrade you end up with libc.so.6 from glibc 2.21 (instead of 2.22) > while libpthread.so.0 is from glibc 2.22. It might be you have a copy if > libc.so.6 somewhere in the locations ld.so is search for. > > Could you therefore please send me the output of "ldd /bin/ls" before > upgrading your system? That should give something like that: > > linux-vdso.so.1 (0x7ffe1013f000) > libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 > (0x7f836df6f000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f836dbcb000) > libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 > (0x7f836d95a000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f836d756000) > /lib64/ld-linux-x86-64.so.2 (0x562bc2437000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x7f836d539000) > > You should check if the libc.so.6 which is used is the one from > /lib/x86_64-linux-gnu or if another one is used. Oh damn...I don't know how this happened, but I had another libc.so.6 in /lib/ (*not* /lib/x86_64-linux-gnu). I removed it and will try upgrading in a snapshot so that if it still breaks I can always revert. - Chiraag signature.asc Description: PGP signature
Bug#817960: libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6
On Sat, Mar 12, 2016 at 12:15:13PM +0100, Aurelien Jarno wrote: > > Could you please give us the exact error message you encountered, > including the symbol name (a photo is fine), so that we can narrow down > the problem? At a first glance it looks like the libc has been partially > upgraded, and that you now have a mix of both 2.21 and 2.22. > > Then we can instruct you how to fix your system, probably using > debian-installer in rescue mode. > > Aurelien > > -- > Aurelien Jarno GPG: 4096R/1DDD8C9B > aurel...@aurel32.net http://www.aurel32.net I fixed my system by downloading 21.9 from snapshot.debian.org and reinstalling libc6, libc6:i386, and all of the other packages (libc-bin, libc6-dev, libc-dev-bin, locales) from a livecd. Well then...when I upgrade within a virtual machine, everything's fine. What is this witchcraft?! - Chiraag signature.asc Description: PGP signature
