Re: Issues with audio after updating

2022-10-12 Thread Maximiliano Estudies
Alsa works fine, I'm able to play sound over jack with software that
let's you pick the audio device (Reaper in my case)

Removing and reinstalling piperwire fixed the issue, but I have no idea why

El lun, 10 oct 2022 a las 23:16, Joel Roth () escribió:
>
> On Sun, Oct 09, 2022 at 10:37:18AM +0200, Maximiliano Estudies wrote:
> > After an update yesterday my audio stopped working. I'm currently on
> > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11
> > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian)
> > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24)
> >
> > The issue seems to be with pulseaudio, but I'm not really sure.
> > pavucontrol shows "no available cards for configuration" on the
> > configuration tab, and ```pactl list cards``` returns nothing but
> > ```pacmd list-cards``` does returns all the available cards. There is
> > a similar behavior when listing the sinks, pactl returns only the
> > dummy sink and pacmd returns the alsa sink, but with state: IDLE
> >
> > I have no idea how to debug this further so any tips are much appreciated!
>
> Hiya Maximiliano,
>
> That the two pulseaudio utilities disagree on what devices
> are present, it seems plausible that some part of pa is to blame.
>
> You may like to verify that your ALSA subsystem is working properly,
> and include this in your bug report.
>
> For that, disable pulseaudio[1],
>
> systemctl --user stop pulseaudio.socket
> systemctl --user stop pulseaudio.service
>
> test play an audio file with aplay, mpv, etc.
> to a device listed by aplay -l, or cat /proc/asound/cards
>
> To start pulse audio again:
>
> systemctl --user start pulseaudio.socket
> systemctl --user start pulseaudio.service
>
> 1. 
> https://askubuntu.com/questions/8425/how-to-temporarily-disable-pulseaudio-while-running-a-game-under-wine
>
> I've not tested this myself.
>
> cheers,
>
> --
> Joel Roth
>



Re: Issues with audio after updating

2022-10-10 Thread Maximiliano Estudies
pipewire-pusle is installed
```
pipewire-pulse/testing,now 0.3.59-1 amd64 [installed,automatic]
  PipeWire PulseAudio daemon
```

El lun, 10 oct 2022 a las 6:07, Dekks Herton () escribió:
>
> Maximiliano Estudies  writes:
>
> > After an update yesterday my audio stopped working. I'm currently on
> > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11
> > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian)
> > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24)
> >
> > The issue seems to be with pulseaudio, but I'm not really sure.
> > pavucontrol shows "no available cards for configuration" on the
> > configuration tab, and ```pactl list cards``` returns nothing but
> > ```pacmd list-cards``` does returns all the available cards. There is
> > a similar behavior when listing the sinks, pactl returns only the
> > dummy sink and pacmd returns the alsa sink, but with state: IDLE
> >
> > I have no idea how to debug this further so any tips are much appreciated!
>
> Hi
>
> Has pipewire-pulse been removed in the update?
>
> My Bookworm audio broke on a new pipewire update in the last week
>
> --
> regards.
>
> Thinkpad T60p 2.33Ghz 2GB SXGA+
>



Re: Issues with audio after updating

2022-10-09 Thread Maximiliano Estudies
pipewire-pulse is installed
```
pipewire-pulse/testing,now 0.3.59-1 amd64 [installed,automatic]
  PipeWire PulseAudio daemon
```

El dom, 9 oct 2022 a las 16:30, Javier Barroso
() escribió:
>
>
>
> El dom., 9 oct. 2022 15:42, Maximiliano Estudies  
> escribió:
>>
>> that's a very good tip, thanks. I'm using testing and the log shows
>> that pulseaudio was updated with some dependencies, I see
>>
>> pulseaudio:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2)
>> pulseaudio-utils:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2)
>> libkf5pulseaudioqt3:amd64 (1.3-2, 1.3-2+b1)
>> pulseaudio-module-jack:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2)
>> were part of the update that broke pulseaudio, so I think I'll use
>> reportbug to report this issue.
>> Thanks for the help!
>
>
> Some weeks ago I needed (on unstable) to install pipewire-pulse to get the 
> sound working again
>
> Regards
>>
>>
>>



Re: Issues with audio after updating

2022-10-09 Thread Maximiliano Estudies
that's a very good tip, thanks. I'm using testing and the log shows
that pulseaudio was updated with some dependencies, I see

pulseaudio:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2)
pulseaudio-utils:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2)
libkf5pulseaudioqt3:amd64 (1.3-2, 1.3-2+b1)
pulseaudio-module-jack:amd64 (15.0+dfsg1-4+b1, 16.1+dfsg1-2)
were part of the update that broke pulseaudio, so I think I'll use
reportbug to report this issue.
Thanks for the help!

El dom, 9 oct 2022 a las 13:39, local10 () escribió:
>
> Oct 9, 2022, 08:37 by maxiestud...@gmail.com:
>
> > After an update yesterday my audio stopped working. I'm currently on
> > Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11
> > (Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian)
> > 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24)
> >
> > The issue seems to be with pulseaudio, but I'm not really sure.
> > pavucontrol shows "no available cards for configuration" on the
> > configuration tab, and ```pactl list cards``` returns nothing but
> > ```pacmd list-cards``` does returns all the available cards. There is
> > a similar behavior when listing the sinks, pactl returns only the
> > dummy sink and pacmd returns the alsa sink, but with state: IDLE
> >
> > I have no idea how to debug this further so any tips are much appreciated!
> >
>
> Are you running Bookworm? Am running Bookworm with seemingly the same kernel 
> but I don't have any issues with audio and it doesn't look like pulseaudio 
> had any upgrades in Bookworm in the last two days.
>
> # uname -a
> Linux tst 5.19.0-2-amd64 #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24) 
> x86_64 GNU/Linux
>
> If you're using aptitude check the aptitude log to see what was upgraded 
> lately:
>
> # less /var/log/aptitude
>
> Regards,
>



Issues with audio after updating

2022-10-09 Thread Maximiliano Estudies
After an update yesterday my audio stopped working. I'm currently on
Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11
(Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for Debian)
2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24)

The issue seems to be with pulseaudio, but I'm not really sure.
pavucontrol shows "no available cards for configuration" on the
configuration tab, and ```pactl list cards``` returns nothing but
```pacmd list-cards``` does returns all the available cards. There is
a similar behavior when listing the sinks, pactl returns only the
dummy sink and pacmd returns the alsa sink, but with state: IDLE

I have no idea how to debug this further so any tips are much appreciated!



Wireless card driver bug

2022-09-10 Thread Maximiliano Estudies
Sep 10 14:51:55 user-thinkpad kernel:  
Sep 10 14:51:55 user-thinkpad kernel: ---[ end trace  ]---

I want to use the reportbug feature but I don't know which package I
should enter. Anyone else having similar issues?
My system settings: Linux version 5.18.0-4-amd64
(debian-ker...@lists.debian.org) (gcc-11 (Debian 11.3.0-5) 11.3.0, GNU
ld (GNU Binutils for Debian) 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC
Debian 5.18.16-1 (2022-08-10)

-- 
Maximiliano Estudies



Re: nft newbie

2022-07-12 Thread Maximiliano Estudies
El mar, 12 jul 2022 a las 14:13, Anssi Saari () escribió:
>
> "Gareth Evans"  writes:
>
> > On Tue 12 Jul 2022, at 10:19, Maximiliano Estudies  
> > wrote:
> >
> >> drop and reject are not equivalent.
> >
> > Fair enough
> >
> > [...]
> >> In most cases it's a best practice to configure all chains with
> >> _policy drop_ and then add rules for the traffic that you want to
> >> allow
> >
> > All the nftables and PF howtos I have found take this approach.
> >
> > Why is it best practice?  Is there any security advantage over rejection?
>
> Not really, to me using DROP is a simplistic view not based in reality.
>
> https://www.chiark.greenend.org.uk/~peterb/network/drop-vs-reject
> covers the pros and cons reasonably with this conclusion:
>
> "DROP offers no effective barrier to hostile forces but can dramatically
> slow down applications run by legitimate users. DROP should not normally
> be used."
>

nft only allows for two possible default policies, DROP or ACCEPT,
thus it isn't possible to configure a chain with default REJECT. Thus
my suggestion to configure default drop (just in case) and a
"catch-all" reject at the bottom of the chain.



Re: nft newbie

2022-07-12 Thread Maximiliano Estudies
drop and reject are not equivalent.
with _reject with icmpx_ you get an icmp response when trying to
access a system and get blocked by the firewall.
with _policy drop_ packets that are not allowed just get silently
dropped and don't give any feedback to the source.

In most cases it's a best practice to configure all chains with
_policy drop_ and then add rules for the traffic that you want to
allow (there are some exceptions but for normal workstations I would
always start with policy drop). For machines that are not exposed to
the internet I also like to configure a reject at the bottom of all
chains, it helps a lot when debugging networking problems to know if
you are getting blocked by the firewall

El mar, 12 jul 2022 a las 1:27, Gareth Evans () escribió:
>
> On Sun 10 Jul 2022, at 06:25, Gareth Evans  wrote:
>
> > Thanks Roger, that also suggests "policy drop" in its nftables examples.
>
> As someone on firewalld-users kindly pointed out, there is
>
> > table inet firewalld {
> > chain filter_INPUT {
> [...]
> > reject with icmpx admin-prohibited   <--- catch-all reject
> > }
>
> which seems equivalent to ufw's qualified "policy drop".
>
> Panic over.
> G
>


-- 
Maximiliano Estudies
VDT Referat Beschallung
+49 176 36784771
omslo.com
maxiestudies.com



Broken login screen after update

2022-06-22 Thread Maximiliano Estudies
Hi,
after the latest updates on Monday I have an issue where the login
screen is buggy after waking up from suspension. The field with the
username is not there and the menus on the corner appear blurry when
clicked. I would like to submit a bug with ```reportbug``` but I don't
know how the package is called. Does anybody happen to know the name
of the package or how I could report the bug?

My system:
Linux version 5.18.0-1-amd64 (debian-ker...@lists.debian.org) (gcc-11
(Debian 11.3.0-3) 11.3.0, GNU ld (GNU Binutils for Debian) 2.38) #1
SMP PREEMPT_DYNAMIC Debian 5.18.2-1 (2022-06-06)

Architecture:x86_64
  CPU op-mode(s):32-bit, 64-bit
  Address sizes: 48 bits physical, 48 bits virtual
  Byte Order:Little Endian
CPU(s):  16
  On-line CPU(s) list:   0-15
Vendor ID:   AuthenticAMD
  Model name:AMD Ryzen 7 PRO 4750U with Radeon Graphics
CPU family:  23
Model:   96
Thread(s) per core:  2
Core(s) per socket:  8
Socket(s):   1
Stepping:1
Frequency boost: enabled
CPU(s) scaling MHz:  82%
CPU max MHz: 1700.
CPU min MHz: 1400.
BogoMIPS:3393.37
Flags:   fpu vme de pse tsc msr pae mce cx8 apic sep
mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx
mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl
nonstop_tsc c
 puid extd_apicid aperfmperf rapl pni
pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave
avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a
misalignsse
  3dnowprefetch osvw ibs skinit wdt tce
topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3
cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2
smep bmi2
 cqm rdt_a rdseed adx smap clflushopt clwb
sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc
cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd
cppc arat npt lb
 rv svm_lock nrip_save tsc_scale vmcb_clean
flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload
vgif v_spec_ctrl umip rdpid overflow_recov succor smca
Virtualization features:
  Virtualization:AMD-V
Caches (sum of all):
  L1d:   256 KiB (8 instances)
  L1i:   256 KiB (8 instances)
  L2:4 MiB (8 instances)
  L3:8 MiB (2 instances)
NUMA:
  NUMA node(s):  1
  NUMA node0 CPU(s): 0-15
Vulnerabilities:
  Itlb multihit: Not affected
  L1tf:  Not affected
  Mds:   Not affected
  Meltdown:  Not affected
  Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
  Spectre v1:Mitigation; usercopy/swapgs barriers and
__user pointer sanitization
  Spectre v2:Mitigation; Retpolines, IBPB conditional,
IBRS_FW, STIBP conditional, RSB filling
  Srbds: Not affected
  Tsx async abort:   Not affected
-- 


-- 
Maximiliano Estudies
VDT Referat Beschallung
+49 176 36784771
omslo.com
maxiestudies.com