Bug#1017976: emacsen-common: Segmentation fault when upgrading emacs to 28.1+1-2

2022-08-23 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#997844: grub2-common: GRUB_THEME setting broken when used with encrypted disks

2021-10-25 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#972286: coreutils: Crash when using globs on a path with non-latin characters

2020-10-15 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#972286: Clarification

2020-10-15 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#972286: coreutils: Crash when using globs on a path with non-latin characters

2020-10-15 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#970869: openvpn: Incorrect handling of multiple instances of template service

2020-09-24 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#968569: cryptsetup-suspend: Set OOMScoreAdjust to -1000 to disable OOM killing for the modified systemd-suspend service

2020-08-17 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#928915: Full log unavailable with -e or -x

2019-05-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#928915: systemd: Full log unavailable with -e or -x

2019-05-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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]:

Bug#928914: Fix for #898892 breaks normal usage

2019-05-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

2019-05-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#918532: Acknowledgement (emacs: Daemon mode does not apply font preferences)

2019-01-07 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#918532: emacs: Daemon mode does not apply font preferences

2019-01-06 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#892585: systemd: can not create user.slice/user session, after upgrade systemd from 237-4 to 238-1/2

2018-03-29 Thread ಚಿರಾಗ್ ನಟರಾಜ್
pecific 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

2018-03-28 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#890299: Comparison for Gubbi versus Lohit Kannada

2018-02-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

2018-02-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#890211: [Pkg-fonts-devel] Bug#890211: fonts-noto-hinted: Certain font characters crash Emacs 25

2018-02-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
; -- > * 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

2016-03-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#817960: libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6

2016-03-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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

Bug#817960: libc6: relocation error version GLIBC_PRIVATE not defined in file libc.so.6

2016-03-12 Thread ಚಿರಾಗ್ ನಟರಾಜ್
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,