Re: Impossible to install extensions with Gnome browser plugin
On gnome you can just run $ *gnome-shell --version* пт, 7 июн. 2024 г. в 22:04, David Wright : > On Fri 07 Jun 2024 at 20:06:27 (+0300), Jan Krapivin wrote: > > Yes, you are right, maybe. Though Debian is probably a rare (if not the > > only) distro that still uses Gnome 43.9, which is, as i use Debian, my > > case. And (maybe) a problem? > > I searched for gnome in https://packages.debian.org/index > and got 65 package matches for bookworm. I repeated for > trixie and got 63 matches. Finally I tried sid and got > 94 matches. However, I failed to find the string 43.9 > on any of these pages. How do you come by it? (I don't > run gnome myself.) > > Cheers, > David. > >
Re: Impossible to install extensions with Gnome browser plugin
Yes, you are right, maybe. Though Debian is probably a rare (if not the only) distro that still uses Gnome 43.9, which is, as i use Debian, my case. And (maybe) a problem? пт, 7 июн. 2024 г. в 20:01, : > Jan Krapivin wrote: > > Thank you for your reply. This topic is not about Debian packages, but > > about a performance of a plugin for browsers, it is not a Debian > > package. > > > > > https://wiki.gnome.org/action/show/Projects/GnomeShellIntegration?action=show=Projects%2FGnomeShellIntegrationForChrome > > > > I am trying to install Gnome extensions with it. They are also not > > Debian packages. > > > > https://extensions.gnome.org/about/ > > So maybe a Gnome forum or list or one about the specific plugin or even > one about the browser is a better place to look for help than a debian > mailing list? > >
Re: Impossible to install extensions with Gnome browser plugin
Thank you for your reply. This topic is not about Debian packages, but about a performance of a plugin for browsers, it is not a Debian package. https://wiki.gnome.org/action/show/Projects/GnomeShellIntegration?action=show=Projects%2FGnomeShellIntegrationForChrome I am trying to install Gnome extensions with it. They are also not Debian packages. https://extensions.gnome.org/about/ The problem can be reproduced only if you use Gnome. For this you must install a special Gnome *BROWSER* plugin and try to install any Gnome extension. It is not a big deal, as I am still able to install Gnome extensions with regular files. But i wonder if it is a universal problem, and if it is not, what is wrong with me, as i haven't done any major changes in OS. пт, 7 июн. 2024 г. в 03:50, George at Clug : > Hi Jan Krapivin, > > I am hoping someone can help you with your answer as I do not use Gnome or > have much experience with Gnome. > > Which Debian package or packages are you installing? > > I found a list of Debian Gnome packages at > https://packages.debian.org/stable/gnome/ > > But I was not able to find a "GNOME Shell integration" package ? > > You said, "i am unable to install new extensions with browser plugin > "GNOME Shell integration"". > > Could you please explain the steps to reproduce your problem, including > installation of the browser plugin package, how in the web browser you add > the extension, and an example extension you were not able to install? > > Thanks, > > George. > > > On Friday, 07-06-2024 at 05:27 Jan Krapivin wrote: > > Guys, can you please spend 30 seconds and check if it is a universal > problem..? > > чт, 6 июн. 2024 г. в 13:41, Jan Krapivin : > >> I have a problem with a Gnome browser plugin. I have even created an >> issue report (see below). >> >> Unfortunately I don't know if I am the only one with this problem. >> >> If you use Debian 12 stable with Gnome, please let me know about your >> experience. >> >> "Hello! I use Debian 12 stable with Gnome 43.9. Recently i have found out >> that i am unable to install new extensions with browser plugin "GNOME Shell >> integration". I have tried different browsers: Firefox stable, Firefox-ESR, >> Chrome. In all of them it is impossible to install a new extension. >> Switching a tumbler from "OFF" to "ON" does nothing. Though it is possible >> to view already installed extensions and switch them off and on. It is also >> possible to install an extension from file. >> >> What i have tried: 1) Switching "Disable version validation" on and off. >> 2) Gnome-shell reinstall. 3) gnome-browser-connector reinstall." >> >> https://gitlab.gnome.org/GNOME/gnome-browser-extension/-/issues/62 >> >
Re: Impossible to install extensions with Gnome browser plugin
Guys, can you please spend 30 seconds and check if it is a universal problem..? чт, 6 июн. 2024 г. в 13:41, Jan Krapivin : > I have a problem with a Gnome browser plugin. I have even created an issue > report (see below). > > Unfortunately I don't know if I am the only one with this problem. > > If you use Debian 12 stable with Gnome, please let me know about your > experience. > > "Hello! I use Debian 12 stable with Gnome 43.9. Recently i have found out > that i am unable to install new extensions with browser plugin "GNOME Shell > integration". I have tried different browsers: Firefox stable, Firefox-ESR, > Chrome. In all of them it is impossible to install a new extension. > Switching a tumbler from "OFF" to "ON" does nothing. Though it is possible > to view already installed extensions and switch them off and on. It is also > possible to install an extension from file. > > What i have tried: 1) Switching "Disable version validation" on and off. > 2) Gnome-shell reinstall. 3) gnome-browser-connector reinstall." > > https://gitlab.gnome.org/GNOME/gnome-browser-extension/-/issues/62 >
Impossible to install extensions with Gnome browser plugin
I have a problem with a Gnome browser plugin. I have even created an issue report (see below). Unfortunately I don't know if I am the only one with this problem. If you use Debian 12 stable with Gnome, please let me know about your experience. "Hello! I use Debian 12 stable with Gnome 43.9. Recently i have found out that i am unable to install new extensions with browser plugin "GNOME Shell integration". I have tried different browsers: Firefox stable, Firefox-ESR, Chrome. In all of them it is impossible to install a new extension. Switching a tumbler from "OFF" to "ON" does nothing. Though it is possible to view already installed extensions and switch them off and on. It is also possible to install an extension from file. What i have tried: 1) Switching "Disable version validation" on and off. 2) Gnome-shell reinstall. 3) gnome-browser-connector reinstall." https://gitlab.gnome.org/GNOME/gnome-browser-extension/-/issues/62
Re: Bluetooth sound problems playing from a web browser
Have you tried a LIVE-version of another Linux distribution? It will be interesting to compare. вс, 7 апр. 2024 г. в 22:30, Richmond : > Richmond writes: > > > Richmond writes: > > > >> When playing videos in a web browser, and sending the sound to a > >> bluetooth speaker (amazon echo) I get playback problems; stuttering, > >> sound quality reduction to AM radio level or lower). These things can > >> clear up after a minute or two, or be reduced. > >> > >> When playing from nvlc however I get no such problems. (I haven't > >> tried vlc so I am not sure if it is just that it is a command line). > >> > >> I have tried google-chrome and firefox-esr. > >> > >> Perhaps there is some other browser which will work? Maybe I need to > >> isolate the process from the browser? I tried pop-out picture on you > >> tube and it improved but there was still stuttering. > > > > I installed Falkon and Konqueror. I tried Falkon and it worked fine, no > > sound problems. But then I tried Google-chrome again and that was > > working fine too, and so was Firefox-esr. The problems have gone away > > and even rebooting doesn't bring them back. Maybe one of those browsers > > brought a better library with it. > > These problems have come back again. I have tried rebooting. I tried > sending the same audio from an android phone and it works fine. How do I > find out what the problems is? I cannot see errors in journalctl > >
Re: Root password strength
чт, 21 мар. 2024 г. в 22:34, Alexander V. Makartsev : > This conclusion seems less than optimal to me. > By condemning yourself to type 12+ character password every time you > 'sudo' would really hurt accessibility and usability of your home computer > and for no good reason. > > If we focus solely on your use case: a login security of a PC at home, > without remote access, then password of your sudo user could be as short and > simple as four numbers, of course unrelated to your date of birth, phone > number, or any other easily guessable sequence of numbers, like '1234'. > Are you speaking only about sudo or root password also? The thing that bothers me are words: "*any* computer (and a fortiori any server) connected to the Internet * is regularly targeted by automated connection attempts"* I am not tech-savvy. Can you say with 100% (90%?) confidence that there is no such thing? That home PC without SSH and whatever complicated is safe (rather safe) from " *automated connection attempts"?* This thread reminded of that topic - https://forums.debian.net/viewtopic.php?t=154002
Re: Root password strength
I must mention that "32 characters" is only my guess. In the Handbook it is said: "The root user's password should be long (12 characters or more) and impossible to guess." Also, i must again say that in my case we speak just about a humble home desktop, without a ""ssh" access"" or whatever complicated. Thank you for your answers and tips. I will make a very strong password for root and a strong one for a user in the sudo group.
Re: Root password strength
> The threats are different for: > > - a laptop that travels and can be stolen > - a desktop that does not leave your residence > - a server that accepts connections from the outside world > > > Check whether you are running ssh: > It is a simple home desktop PC *@deb:~$ /sbin/service ssh status* *Unit ssh.service could not be found.* *@deb:~$ sudo /sbin/service ssh status* *[sudo] password for ***: * *Unit ssh.service could not be found.*
Re: Root password strength
> Do you have some kind of remote access enabled or do you intend to in > the near future? > No and no. Its just a simple home PC. > > If not, then you do not need to worry. Even less if you have a firewall > to block any service that might appear by mistake. > I have UFW (gufw) enabled. Thank you.
Root password strength
I read Debian Administrator's handbook now. And there are such words: The root user's password should be long (12 characters or more) and impossible to guess. Indeed, any computer (and a fortiori any server) connected to the Internet is regularly targeted by automated connection attempts with the most obvious passwords. Sometimes it may even be subject to dictionary attacks, in which many combinations of words and numbers are tested as password. Avoid using the names of children or parents, dates of birth, etc.: many of your co-workers might know them, and you rarely want to give them free access to the computer in question. The thing is my password is very easy now, and i haven't thought about *"automated connection attempts"*, that sounds rather... scary? My password is easy because i am not afraid of direct physical access to the computer. But... if there is a serious network danger, then i should change my password of course. But how strong it should be? If we speak about network attacks... it should be like 32 symbols with special symbols? Or this paragraph in a handbook is rather paranoid? I have activated sudo now for my regular user. Can it (password of regular user) be less sophisticated than root password? Because it would be rather difficult to enter 32 symbols every time i wake my PC after suspend.
Re: Bluetooth sound problems Debian 12 GNOME
Good news. Looks like I have solved the problem. As a last resort I have bought another one wi-fi receiver, third one. It has *Realtek RTL8763BW* chip <https://www.realtek.com/en/products/communications-network-ics/item/rtl8763b> and *two antennas*. And finally all works fine. I have spent some hours, using Bluetooth headphones, waiting for problems, but they hadn’t occur. Small problem is that LTS Kernel 6.1 doesn’t support this device, so I have used Liquorix kernel, which I have installed earlier. Though, I don’t need this kernel, as it haven’t helped me with sound interrupts, which was my hope at first. So… I bought more old Wi-fi receiver with *Realtek RTL8761BUV* chip with antenna and it also works fine, and also works with stable 6.1 kernel. I am glad that situation found its resolution, though it is strange for me that USB-dongle Bluetooth receiver (I don’t know the exact model) and receiver on an internal wi-fi adapter (AX 210) have worked so poorly both. Though I was in the distance not more than 2 meters from receiver. Thanks for help пт, 15 мар. 2024 г. в 05:21, Max Nikulin : > On 14/03/2024 19:06, Jan Krapivin wrote: > > > > What do you think about QUANT parameter in */pw-top/*? Can it influence > > sound quality? I wasn't able to change it with > > > > pw-metadata -n settings 0 clock.force-quantum 2048 > > Sorry, my experience with tuning PipeWire is limited to switching audio > profiles (A2DP codecs, HSF) from UI. > > I think in you case it would be more productive to enable debug logs > either in bluetoothd or PipeWire to find either the host or the device > drops or lost connections causing pauses till reconnect. > > >
Re: Bluetooth sound problems Debian 12 GNOME
> You may try to discriminate hardware/software issues when you comparing > different laptops by booting various live images (GNOME, xfce, etc.). > I will try... Thank you. What do you think about QUANT parameter in *pw-top*? Can it influence sound quality? I wasn't able to change it with *pw-metadata -n settings 0 clock.force-quantum 2048*
Re: Bluetooth sound problems Debian 12 GNOME
> Run the command as root, but you already have enough keywords to search > in bug reports and discussions related to PipeWire and pulseaudio. The > latter may have some workarounds for specific models of headphones. Thanks, i will try to research this topic. > PipeWire mailing list or forum may be a better place to discuss the issue. > OK While watching *pactl subscribe *command output, i have noticed that there was a change from sink 414 to sink 213 when sound interrupt occurred "Event 'change' on sink-input #414 Event 'change' on sink-input #414 Event 'change' on sink-input #414 Event 'change' on sink-input #213 Event 'change' on sink-input #213 Event 'change' on sink-input #213" Can this information be of any help?
Re: Bluetooth sound problems Debian 12 GNOME
It is strange. I can see in a Debian mailing list an answer - *From*: Ottavio Caruso - *Date*: Mon, 11 Mar 2024 16:50:45 + "Not sure if this is your case, I had the same problem but I upgraded from 11 to 12. The transition from pulse to pipewire was not smooth. So I nuked anything *pulse* and *bluetooth* and reinstalled from scratch using the Debian guide: https://wiki.debian.org/PipeWire Is this a brand new installation or an upgrade?" But i can't see it in my mailbox *ANSWER* No, this is a clean new installation. And it looks like i have the same problem on another laptop with Debian 12 XFCE (Pulseaudio). But the problem is with *TWO* headsets, so i am in question whats happening with Debian, because Linux Mint and Android works fine... пн, 11 мар. 2024 г. в 23:48, Jan Krapivin : > Hello again. I have used *pactl subscribe *command and i think that in > the moment of sound interrupt there are the corresponding lines: > > "Event 'remove' on sink-input #353 > Event 'new' on sink-input #358 > Event 'change' on sink-input #358" > > As for journald i have a lot of such errors, but they don't influence the > audio quality: > > "Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem > not available: AT+XIAOMI=1,1,102,85,88,27,174" > > There are some other mentions of the bluetooth/headphones, but they don't > meet the moment of sound issues. Full journald -f log is in an attachment. > > I must say that i had an opportunity today to test a laptop with Debian 12 > XFCE laptop with Pulseaudio and the problem is the same there. But, as i > said, on a laptop with Linux Mint XFCE everything is fine. That's strange. > What is the main difference between Linux Mint and Debian here..? > > I also tried Liquorix 6.7 kernel but it didn't help. > > Thanks. >
Re: Bluetooth sound problems Debian 12 GNOME
Hello again. I have used *pactl subscribe *command and i think that in the moment of sound interrupt there are the corresponding lines: "Event 'remove' on sink-input #353 Event 'new' on sink-input #358 Event 'change' on sink-input #358" As for journald i have a lot of such errors, but they don't influence the audio quality: "Mar 11 22:20:13 deb wireplumber[1357]: RFCOMM receive command but modem not available: AT+XIAOMI=1,1,102,85,88,27,174" There are some other mentions of the bluetooth/headphones, but they don't meet the moment of sound issues. Full journald -f log is in an attachment. I must say that i had an opportunity today to test a laptop with Debian 12 XFCE laptop with Pulseaudio and the problem is the same there. But, as i said, on a laptop with Linux Mint XFCE everything is fine. That's strange. What is the main difference between Linux Mint and Debian here..? I also tried Liquorix 6.7 kernel but it didn't help. Thanks. journalctl -f Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Mar 11 21:28:16 deb wireplumber[1357]: RFCOMM receive command but modem not available: AT+BTRH? Mar 11 21:28:16 deb wireplumber[1357]: RFCOMM receive command but modem not available: AT+XIAOMI=1,1,102,100,100,27,174 Mar 11 21:29:21 deb systemd[1331]: Started app-gnome-gnome\x2dterminal-6829.scope - Application launched by gsd-media-keys. Mar 11 21:29:21 deb dbus-daemon[1367]: [session uid=1000 pid=1367] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.131' (uid=1000 pid=6829 comm="gnome-terminal") Mar 11 21:29:21 deb systemd[1331]: Starting gnome-terminal-server.service - GNOME Terminal Server... Mar 11 21:29:22 deb dbus-daemon[1367]: [session uid=1000 pid=1367] Successfully activated service 'org.gnome.Terminal' Mar 11 21:29:22 deb systemd[1331]: Started gnome-terminal-server.service - GNOME Terminal Server. Mar 11 21:29:22 deb systemd[1331]: Started vte-spawn-82cf01f4-467e-44e1-b0e3-19af9cb02a2a.scope - VTE child process 6864 launched by gnome-terminal-server process 6834. Mar 11 21:30:27 deb systemd[1331]: Started app-gnome-gnome\x2dterminal-7042.scope - Application launched by gsd-media-keys. Mar 11 21:30:27 deb systemd[1331]: Started vte-spawn-6e59a663-467e-40c5-9553-ad6b513aeecb.scope - VTE child process 7048 launched by gnome-terminal-server process 6834. Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Changing wallpaper... Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Current wallpaper "a2.jpg" Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Wallpapers in queue: 8 Mar 11 21:33:03 deb gnome-shell[1624]: Wallpaper Slideshow: Next slide in 600 seconds. Mar 11 21:41:51 deb gnome-shell[1624]: JS ERROR: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: No such property “IconAccessibleDesc” _promisify/proto[asyncFunc]/
Re: Bluetooth sound problems Debian 12 GNOME
пн, 11 мар. 2024 г. в 07:50, Max Nikulin : > > Are there anything in journalctl output (executed as root) around these > events? > I guess that no, but i will recheck. > Is XFCE configured to use pulseaudio or PipeWire as GNOME? > Pulseaudio > Another option might be LC3 codec from Bluetooth LE (5.2 Basic Audio > Profile) if it is supported by the headphones. > Unfortunately it's not supported. > Either a software/hardware bug or some piece of software disables power > saving for handsfree/headset profiles to achieve low latency, but for > A2DP device tries to sleep after some period of time. > Hm, i will try to research that, thank you. Arch Linux wiki pages have long troubleshooting sections. > Yes, I saw but found nothing relatable to my view. Last resort might be dumping bluetooth traffic, but perhaps it is better > to ask in some mailing list or forum more close to Bluetooth stack > developers. > I have installed Wireshark, but somehow i can't find bluetooth connection to capture (https://forums.debian.net/viewtopic.php?p=795020#p795020)
Bluetooth sound problems Debian 12 GNOME
Hello! I have a problem with sound quality when using bluetooth headphones
on Debian 12 GNOME.
Every ~20 minutes, sometimes less, sometimes more, sound interrupts for a
1-5 seconds with complete silence.
At first I thought that problem can be in the headphones, though it have
worked fine with Android phone and Linux Mint XFCE on a other laptop.
So I bought another headphones with support of different codecs: SBC, AAC,
and AptX.
And I have the same problem, but now I hear not only silence but also a
crackling, when sound interrupts.
I tried different codecs, including AAC (
https://forums.debian.net/viewtopic.php?p=777598#p777598). But the problem
prevails.
Yes, I must of course mention that there is absolutely no problems, when
using non-bluetooth devices like speakers, headphones etc.
The only workaround is to use HSP mSBC codec in Heandsfree mode, but the
sound is awful.
Though in mSBC there are no interruptions. I wonder why mSBC works fine and
SBC no..?
My system is (inxi)
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-10:3 chip-ID: 8087:0032 class-ID: e001
Report: hciconfig ID: hci0 rfk-id: 0 state: up address:
Info: acl-mtu: 1021:4 sco-mtu: 96:6 link-policy: rswitch sniff
link-mode: peripheral accept service-classes: rendering, capturing, object
transfer, audio, telephony
Audio:
Device-1: Intel Cannon Lake PCH cAVS driver: snd_hda_intel
Device-2: NVIDIA GP107GL High Definition Audio driver: snd_hda_intel
Device-3: Creative Sound Blaster Play! 3 type: USB
driver: hid-generic,snd-usb-audio,usbhid
API: ALSA v: k6.1.0-18-amd64 status: kernel-api
Server-1: PipeWire v: 0.3.65 status: active
What have i tried?
Creating choppy-under-load.conf file in
/home/ja/.config/pipewire/pipewire-pulse.conf.d/ with
“context.properties = {
default.clock.quantum = 8192
default.clock.min-quantum = 8192
}”
Creating switch-on-connect.conf file with
pulse.cmd = [
{ cmd = "load-module" args = "module-always-sink" flags = [ ] }
{ cmd = "load-module" args = "module-switch-on-connect" }
]
Unfortunately I have no ideas what to try further as I am not a
power-user/techy.
I have tried to use PulseAudio, pipe-wire media session and not
Wireplumber, backported version of PipeWire, but all these attempts left me
with GDM/Gnome removed from the system! As Gnome now have
Pipewire/Wireplumber as dependency.
I want to try all options possible (if any) before I ditch Gnome in favour
of DE, that supports Pulseaudio.
P.S. I have tried two different bluetooth hardware modules, one on a Wi-fi
chip and one USB-stick, with no difference.
