You are not logged in.
I launched telegram under AppArmor and noticed that every time it starts it tries to execute /usr/bin/bash
type=AVC msg=audit(1540761706.295:237663): apparmor="DENIED" operation="exec" profile="/usr/bin/telegram-desktop" name="/usr/bin/bash" pid=2591 comm="telegram-deskto" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0
Version from the official site doesn't do this, nor I found anything about executing /usr/bin/bash in sources.
Did someone build his own code to repository?
Offline
I can't answer your topic question, and I'm not sure what your last question means, but you can check the build files that are used to create the package here: https://git.archlinux.org/svntogit/comm … am-desktop (or manually navigate to them by clicking the Packages link at the top of this page -> search -> click package name -> click "source files" link on the top right of page). I can't see any mention of /usr/bin/bash in any of the Arch files, so I guess this is something that upstream does (maybe /usr/bin/telegram-desktop is a wrapper script?). You can checkout the build files and download the source files (and even build the package yourself) if you want to investigate further: https://wiki.archlinux.org/index.php/Arch_Build_System
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
Thanks
maybe /usr/bin/telegram-desktop is a wrapper script?
No
> file (which telegram-desktop)
/usr/bin/telegram-desktop: ELF 64-bit LSB shared object, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=1f19b65a5783829a72a1b5955583616e24e366b4, strippedOffline
strace output:
[pid 1766] execve("/bin/sh", ["sh", "-c", "/usr/bin/jackd -l"], 0x55fdf7431800 /* 39 vars */) = 0
[pid 1766] execve("/usr/bin/jackd", ["/usr/bin/jackd", "-l"], 0x55db09a5ed80 /* 40 vars */) = 0Offline
If you download the PKGBUILD arch is using then use makepkg to build it locally or preferably in a clean chroot.
Check that the string jackd is not present in the sources or the built binary. Does the locally built package still call jackd?
Offline