Re: [arch-general] Why are Archlinux packages stripped of (debugging) symbols?

2020-01-22 Thread Łukasz Michalski
On 22/01/2020 14.36, Justin Capella via arch-general wrote:
> point. Maybe one day users could submit coredumps / backtraces to a
> webservice that would reference the symbols, and "bucket" the traces to
> help triage/identify unique crashes
> 

For me it would be better if I could just download debugging symbols using 
pacman and analyze coredumps locally.

Regards,
Łukasz


Re: [arch-general] Why are Archlinux packages stripped of (debugging) symbols?

2020-01-22 Thread Justin Capella via arch-general
The reason I'd really like native packages to be built with split symbols
even if they aren't included in the package but available through some
other means... Is so that bug wranglers can more easily make sense of
traces/coredumpctl info output, where rebuilding the package would just be
a hassle and potentially result in different symbols, which defeats the
point. Maybe one day users could submit coredumps / backtraces to a
webservice that would reference the symbols, and "bucket" the traces to
help triage/identify unique crashes


Re: [arch-general] Status of WPA3

2020-01-22 Thread Genes Lists via arch-general
On 1/22/20 7:49 AM, Bjoern Franke via arch-general wrote:
> Hi,
> 
> recently AVM provided a beta-Firmware for Fritzboxes which support WPA3.
...

In addition to above, iwd has support for WPA3 - may be worth switching
over from wpa_supp to iwd and see if it works for you (i've been using
it for some time now and it's been working well, though I have no access
to test WPA3

Using it with network manager is very easy to turn on - just create:
cat /etc/NetworkManager/conf.d/wifi_backend.conf
[device]
wifi.backend=iwd

And restart nm. Let us know if you get it working.


[arch-general] Status of WPA3

2020-01-22 Thread Bjoern Franke via arch-general
Hi,

recently AVM provided a beta-Firmware for Fritzboxes which support WPA3.
Unfortunately, our wpa_supplicant seems not be capable of WPA3:

https://bugs.archlinux.org/task/57413

When setting explicitly WPA3 in NetworkManager, my laptop is unable to
connect to my WPA2/WPA3-wifi. I assume it is caused by the missing SAE
support, or do I miss something? The assumption is caused by
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/9

Best Regards
Bjoern


Re: [arch-general] Eduroam madness with iwd

2020-01-22 Thread Christian Hesse
Riccardo Paolo Bestetti via arch-general  on Wed,
2020/01/22 11:45:
> And the following error in the system journal:
> failed to load /home/random/.cat_installer/ca.pem

The certificate can not be loaded as iwd.service has ProtectHome=yes set.
Move it to a location where iwd can read it.
-- 
main(a){char*c=/*Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/*Best regards my address:*/=0;b=c[a++];)
putchar(b-1/(/*Chriscc -ox -xc - && ./x*/b/42*2-3)*42);}


pgpVB2VSg30tV.pgp
Description: OpenPGP digital signature


Re: [arch-general] pacman error when installing

2020-01-22 Thread Maykel Franco via arch-general
El mié., 22 ene. 2020 a las 9:44, Ralf Mardorf via arch-general
() escribió:
>
> On Wed, 2020-01-22 at 09:29 +0100, Maykel Franco via arch-general wrote:
> > error: failed to commit transaction (conflicting files)
>
> First consider to check which package/s contain the conflicting files?
> Maybe obsolete packages could be removed.
>
> pacman -Qo /path/file-name


Example:

pacman -Qo /usr/bin/pprof
 1 ↵  10021  12:47:27
error: No package owns /usr/bin/pprof


[arch-general] Eduroam madness with iwd

2020-01-22 Thread Riccardo Paolo Bestetti via arch-general
Hi!

I'm trying to configure iwd to connect to Eduroam. My home istitution requires 
EAP-TTLS authentication with PAP Phase 2.

I have the following configuration file:

[Security]
EAP-Method=TTLS
EAP-TTLS-CACert=/home/random/.cat_installer/ca.pem
EAP-TTLS-ServerDomainMask=*.unipmn.it
EAP-TTLS-Phase2-Method=Tunneled-PAP
EAP-TTLS-Phase2-Identity=theUser
EAP-TTLS-Phase2-Password=thePassword

[Settings]
AutoConnect=true

When I try to connect with iwd started as a systemd unit, I get the following 
error in iwctl:
Not configured.
And the following error in the system journal:
failed to load /home/random/.cat_installer/ca.pem
(the certificate is valid and is in the required PEM format - I checked it with 
the openssl command and it also works with different network daemons)

When I try to connect with iwd started manually with /usr/lib/iwd/iwd -d, I get 
the following error instead:
Operation failed.
And idw outputs:
4-Way handshake failed for ifindex: 3, reason: 23.

I ran out of debugging ideas! Can anyone help?

- Riccardo


Re: [arch-general] pacman error when installing

2020-01-22 Thread Ralf Mardorf via arch-general
On Wed, 2020-01-22 at 09:29 +0100, Maykel Franco via arch-general wrote:
> error: failed to commit transaction (conflicting files)

First consider to check which package/s contain the conflicting files?
Maybe obsolete packages could be removed.

pacman -Qo /path/file-name


[arch-general] pacman error when installing

2020-01-22 Thread Maykel Franco via arch-general
Before, with -f options or --force, it resolved it. And now, invalid option.

error: failed to commit transaction (conflicting files)
libmad: /usr/include/mad.h exists in filesystem
libmad: /usr/lib/libmad.so exists in filesystem
libmad: /usr/lib/libmad.so.0 exists in filesystem
libmad: /usr/lib/libmad.so.0.2.1 exists in filesystem
libmad: /usr/lib/pkgconfig/mad.pc exists in filesystem
gperftools: /usr/bin/pprof exists in filesystem
gperftools: /usr/include/google/heap-checker.h exists in filesystem
gperftools: /usr/include/google/heap-profiler.h exists in filesystem
gperftools: /usr/include/google/malloc_extension.h exists in filesystem
gperftools: /usr/include/google/malloc_extension_c.h exists in filesystem
gperftools: /usr/include/google/malloc_hook.h exists in filesystem
gperftools: /usr/include/google/malloc_hook_c.h exists in filesystem
gperftools: /usr/include/google/profiler.h exists in filesystem
gperftools: /usr/include/google/stacktrace.h exists in filesystem
gperftools: /usr/include/google/tcmalloc.h exists in filesystem
gperftools: /usr/include/gperftools/heap-checker.h exists in filesystem
gperftools: /usr/include/gperftools/heap-profiler.h exists in filesystem
gperftools: /usr/include/gperftools/malloc_extension.h exists in filesystem
gperftools: /usr/include/gperftools/malloc_extension_c.h exists in
filesystem
gperftools: /usr/include/gperftools/malloc_hook.h exists in filesystem
gperftools: /usr/include/gperftools/malloc_hook_c.h exists in filesystem
gperftools: /usr/include/gperftools/nallocx.h exists in filesystem
gperftools: /usr/include/gperftools/profiler.h exists in filesystem
gperftools: /usr/include/gperftools/stacktrace.h exists in filesystem
gperftools: /usr/include/gperftools/tcmalloc.h exists in filesystem
gperftools: /usr/lib/libprofiler.so exists in filesystem
gperftools: /usr/lib/libprofiler.so.0 exists in filesystem
gperftools: /usr/lib/libprofiler.so.0.4.18 exists in filesystem
gperftools: /usr/lib/libtcmalloc.so exists in filesystem
gperftools: /usr/lib/libtcmalloc.so.4 exists in filesystem
gperftools: /usr/lib/libtcmalloc.so.4.5.3 exists in filesystem
gperftools: /usr/lib/libtcmalloc_and_profiler.so exists in filesystem
gperftools: /usr/lib/libtcmalloc_and_profiler.so.4 exists in filesystem
gperftools: /usr/lib/libtcmalloc_and_profiler.so.4.5.3 exists in filesystem
gperftools: /usr/lib/libtcmalloc_debug.so exists in filesystem
gperftools: /usr/lib/libtcmalloc_debug.so.4 exists in filesystem
gperftools: /usr/lib/libtcmalloc_debug.so.4.5.3 exists in filesystem
gperftools: /usr/lib/libtcmalloc_minimal.so exists in filesystem
gperftools: /usr/lib/libtcmalloc_minimal.so.4 exists in filesystem
gperftools: /usr/lib/libtcmalloc_minimal.so.4.5.3 exists in filesystem
gperftools: /usr/lib/libtcmalloc_minimal_debug.so exists in filesystem
gperftools: /usr/lib/libtcmalloc_minimal_debug.so.4 exists in filesystem
gperftools: /usr/lib/libtcmalloc_minimal_debug.so.4.5.3 exists in
filesystem
gperftools: /usr/lib/pkgconfig/libprofiler.pc exists in filesystem
gperftools: /usr/lib/pkgconfig/libtcmalloc.pc exists in filesystem
gperftools: /usr/lib/pkgconfig/libtcmalloc_debug.pc exists in filesystem
gperftools: /usr/lib/pkgconfig/libtcmalloc_minimal.pc exists in filesystem
gperftools: /usr/lib/pkgconfig/libtcmalloc_minimal_debug.pc exists in
filesystem
gperftools: /usr/share/doc/gperftools/AUTHORS exists in filesystem
gperftools: /usr/share/doc/gperftools/COPYING exists in filesystem
gperftools: /usr/share/doc/gperftools/ChangeLog exists in filesystem
gperftools: /usr/share/doc/gperftools/ChangeLog.old exists in filesystem
gperftools: /usr/share/doc/gperftools/INSTALL exists in filesystem
gperftools: /usr/share/doc/gperftools/NEWS exists in filesystem
gperftools: /usr/share/doc/gperftools/README exists in filesystem
gperftools: /usr/share/doc/gperftools/README_windows.txt exists in
filesystem
gperftools: /usr/share/doc/gperftools/TODO exists in filesystem
gperftools: /usr/share/doc/gperftools/cpuprofile-fileformat.html exists in
filesystem
gperftools: /usr/share/doc/gperftools/cpuprofile.html exists in filesystem
gperftools: /usr/share/doc/gperftools/designstyle.css exists in filesystem
gperftools: /usr/share/doc/gperftools/heap-example1.png exists in
filesystem
gperftools: /usr/share/doc/gperftools/heap_checker.html exists in
filesystem
gperftools: /usr/share/doc/gperftools/heapprofile.html exists in filesystem
gperftools: /usr/share/doc/gperftools/index.html exists in filesystem
gperftools: /usr/share/doc/gperftools/overview.dot exists in filesystem
gperftools: /usr/share/doc/gperftools/overview.gif exists in filesystem
gperftools: /usr/share/doc/gperftools/pageheap.dot exists in filesystem
gperftools: /usr/share/doc/gperftools/pageheap.gif exists in filesystem
gperftools: /usr/share/doc/gperftools/pprof-test-big.gif exists in
filesystem
gperftools: /usr/share/doc/gperftools/pprof-test.gif exists in filesystem
gperftools: /usr/share/doc/gperftools/pprof-vsnprintf-big.gif exists in