Re: Reporte bug

[Camaleón]

El 2023-01-29 a las 14:40 -0500, juan martinez escribió:

> es mi primera vez pasandome a debian testing y me gusto mucho debian, pero
> me pasa algo curioso, cada vez que trato de cambiar los iconos en el menú
> de configuración de kde se cierra de forma inesperada, no se si sea un bug
> o si ya esta reportada perdonen en si no es bug pero soy nuevo en este
> mundo

Si buscas en Google verás que aparecen varios resultados de cierres del 
panel de control de KDE:

https://www.google.com/search?q=kde+system+settings+crashes
https://www.google.com/search?q=kde+icon+theme+change+crashes

¿Se cierra siempre independientemente del tipo de iconos que 
selecciones o sólo cuando seleccionas un estilo de iconos 
concreto?

Como tienes la versión de pruebas, quizá algún paquete se haya 
actualizado y esté dando guerra. 

Puedes probar a crear un nuevo usuario en el sistema (limpio), iniciar 
sesión en KDE con el nuevo usuario y ver si le sucede lo mismo para 
descartar algún problema de configuraciones.

Si al nuevo usuario también le pasa igual, podría ser problema de alguna 
biblioteca.

Puedes poner un bug en Debian o en KDE, los pasos por aquí:

https://bugs.kde.org/
https://www.debian.org/Bugs/Reporting

Saludos,

-- 
Camaleón 

Re: Xfce destop environment

[David]

On Mon, 2023-01-30 at 00:07 -0600, William Torrez Corea wrote:
> What happened with my desktop environment?
> 
> My desktop environment has problems, the title bar is hidden.

Well, William, from your extensive description of the situation, you
may well have enabled full-screen or have a resolution problem.
It could be anything.
When did this first start happening?
Is there any possible causative action you might have taken which
initiated this behaviour?
Cheers!

Xfce destop environment

[William Torrez Corea]

What happened with my desktop environment?

My desktop environment has problems, the title bar is hidden.
-- 

With kindest regards, William.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: Web page management. Was: Re: Debian release criteria.

[Celejar]

On Fri, 20 Jan 2023 14:14:22 -0500
Dan Ritter  wrote:

> pe...@easthope.ca wrote: 
> > Unwieldly References list truncated.
> > 
> > From: Stefan Monnier 
> > Date: Sat, 07 Jan 2023 12:45:52 -0500
> > > I use uMatrix, which I find strikes a fairly good balance between
> > > keeping sites working and letting me control how much crap is loaded.
> > 
> > Another helpful add-on.  Thanks!
> > 
> > A feature (gingerbread) I'd rather not have in Wikipedia is the popup 
> > article preview from hovering the pointer on a link.  Can uMatrix 
> > block that?  How?
> 
> Yes, because uBlock Origin is the less capable sibling and uBO
> can do that. Just block JavaScript on the wikipedia.org domain.
> The site remains largely functional but does not do previews.

For those who may not be aware, the developer of uBlock Origin and
uMatrix, Raymond Hill, has ceased work on uMatrix:

https://github.com/uBlockOrigin/uMatrix-issues/issues/291#issuecomment-694988696
https://github.com/gorhill/uMatrix
https://www.ghacks.net/2020/09/20/umatrix-development-has-ended/

-- 
Celejar

Re: Vulnerable git in bullseye - what's the process?

[David]

On Sat, 28 Jan 2023 at 03:56, Tixy  wrote:
> On Fri, 2023-01-27 at 11:28 +, Brad Rogers wrote:
> > On Fri, 27 Jan 2023 11:36:12 +0100 "Sijmen J. Mulder"  
> > wrote:

> > > I was surprised to find that the recent git vulnerability hasn't yet
> > > been addressed in Bullseye:

> > > https://security-tracker.debian.org/tracker/CVE-2022-41903

> > The security-tracker CVE page you cited has links to all the
> > information you requested.

> Does it? It links to a bug which says it's been fixed in sid. And the
> PTS shows it was fixed yesterday in old-stable and sid. But no sign I
> can see that anything is being done for stable (Bullseye) which is what
> Sijmen asked about. (I wouldn't know where to look for stable security
> update activity).

Announcement today regarding Stable (Bullseye) distribution:
  https://lists.debian.org/debian-security-announce/2023/msg00022.html

Re: laptop frozen when opening apps, debian testing with gnome

[Shalom Ben-Zvii Kazaz]

OK, I did it.
i didn't wait for the freeze to happen randomly because it may take time, i
tried to open zoom which always causes a freeze, It started only in the
past few days and after a full-upgrade, i use zoom regularly and there was
no problem before the last full-upgrade. its debian testing.
I opened zoom with super key, search for zoom and enter. the computer
freezes immediately.

there was nothing in dmesg or /var/log/messages before the freeze,
this is what was in journalctl and top, i don't know how to tell if there
is something suspicious.

journalctl
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Settings.SearchProvider' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Contacts.SearchProvider' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Nautilus' requested by ':1.35' (uid=1000
pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Calculator.SearchProvider' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.Characters' requested by ':1.35'
(uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.clocks' requested by ':1.35' (uid=1000
pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.seahorse.Application' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating via systemd: service name='org.gnome.Terminal'
unit='gnome-terminal-server.service' requested by ':1.35' (uid=1000
pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Settings.SearchProvider'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Calculator.SearchProvider'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.clocks'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.seahorse.Application'
Jan 30 00:01:49 xps-debian nautilus[9317]: Connecting to
org.freedesktop.Tracker3.Miner.Files
Jan 30 00:01:49 xps-debian systemd[3253]: Starting GNOME Terminal Server...
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Nautilus'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Contacts.SearchProvider'
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Characters'
Jan 30 00:01:49 xps-debian nautilus[9317]: g_hash_table_foreach: assertion
'hash_table != NULL' failed
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.DiskUtility' requested by ':1.170'
(uid=1000 pid=9317 comm="/usr/bin/nautilus --gapplication-service")
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.DiskUtility'
Jan 30 00:01:49 xps-debian gnome-character[9321]: JS LOG: Characters
Application started
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.Terminal'
Jan 30 00:01:49 xps-debian systemd[3253]: Started GNOME Terminal Server.
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Activating service name='org.gnome.seahorse.Application' requested by
':1.35' (uid=1000 pid=3523 comm="/usr/bin/gnome-shell")
Jan 30 00:01:49 xps-debian gnome-shell[3523]: Received error from D-Bus
search provider org.gnome.Terminal.desktop: Gio.DBusError:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist
at path “/org/gnome/Terminal/SearchProvider”
Jan 30 00:01:49 xps-debian dbus-daemon[3297]: [session uid=1000 pid=3297]
Successfully activated service 'org.gnome.seahorse.Application'
Jan 30 00:01:50 xps-debian gnome-shell[3523]: Received error from D-Bus
search provider org.gnome.Terminal.desktop: Gio.DBusError:
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist
at path “/org/gnome/Terminal/SearchProvider”
Jan 30 00:01:50 xps-debian PackageKit[2312]: resolve transaction
/32688_aaecaebb from uid 1000 finished with cancelled after 323ms

Re: apt search dotfiles

[Geert Stappers]

On Fri, Jan 27, 2023 at 03:17:46PM +0100, Paul van der Vlis wrote:
> Op 12-01-2023 om 22:40 schreef Geert Stappers:
> > Van de
> > > > Wat is zoal jullie favoriete tool om "dotfiles" te beheren?
> > is de bedoeling om wat tips te krijgen hoe met "dotfiles" om te gaan.
> > Lang en eigenlijk nog steeds beschouw ik dotfiles als een kussen om
> > op te zitten. Ik wil gewoon op het kussen zitten, niet bezig zijn met
> > het kussen op te schudden en goed te leggen. Recent inzicht is dat het
> > toch wel fijn is om op meerdere plaatsen lekker zittende kussens te
> > hebben liggen. Misschien ben ik opzoek naar hoe makkelijk "kussens"
> > op meerdere servers te krijgen. Ik denk dan ook dat ik benieuwd ben
> > naar hoe jullie omgaan met aanpassing op meerdere servers van dotfiles.
> 
> Eigenlijk doe ik niet zo heel veel met dotfiles. Maar wat je zou kunnen
> overwegen is van de inhoud van een mooie homedirectory een tarbal te maken,
> en deze op een website te zetten. Als je dan een mooie situatie wilt hebben
> zou je deze kunnen downloaden en dan uitpakken.
> 
> Ik gebruik in veel gevallen een script, zoiets:
> wget https://vandervlis.nl/script
> bash script
> 
> In dat script kan natuurlijk o.a. staan dat je een tarbal download en
> uitpakt, of eerst de huidige dotfiles backupped, e.d.

Het idee van een tarbal op een server ga ik verder uitwerken.
(Dank voor de tip.) 

> Je kunt een script als gewone gebruiker aanroepen, maar ook als root.
> Zelf doe ik het als root en dan staat er ook zoiets in:
> 
> lijst=`ls -1 /home`
> for user in $lijst; do
>bla
> done
> 
> Je zou het ook als root voor een bepaalde user kunnen doen, iets als:
> bash script piet
> 
> Wat ook leuk is om de directory "/etc/skel" aan te passen. Daarin staan alle
> dotfiles die in de homedirectory van een nieuwe gebruiker komen.
> 
> Groet,
> Paul


Groeten
Geert Stappers
-- 
Silence is hard to parse

Re: Reporte bug

[Leo Marín]

En mi caso pasa cuando selecciono "Decoración de las ventanas" al
seleccionar se cierra inmediatamente con error,

y otra cosa que pasa y no se si será solo en mi caso, es que desde hace
unas semanas tengo un stuttering cada tanto,
dura algunos segundos y después continua normal, y no hablo de la parte del
video, es en todo el equipo en general (va a tirones por algunos segundos),

en la laptop se nota más, descarté el navegador y el driver de nvidia,
usando el driver amdgpu se nota un poco menos pero sigue pasando,
en el equipo de escritorio pasa igual con grafica solo de amd, pero si es
bastante menos,

saludos.


El dom, 29 ene 2023 a las 16:57, juan martinez ()
escribió:

> hola chicos,
>
> es mi primera vez pasandome a debian testing y me gusto mucho debian, pero
> me pasa algo curioso, cada vez que trato de cambiar los iconos en el menú
> de configuración de kde se cierra de forma inesperada, no se si sea un bug
> o si ya esta reportada perdonen en si no es bug pero soy nuevo en este
> mundo
>
> --
> *Juan C. Martínez Anaya*
> * Ingeniero  civil*
> "Se oyen pasos de alguien que no llega nunca "
>
>
>

-- 
L.J.Marín
Usando: Debian Testing

Reporte bug

[juan martinez]

hola chicos,

es mi primera vez pasandome a debian testing y me gusto mucho debian, pero
me pasa algo curioso, cada vez que trato de cambiar los iconos en el menú
de configuración de kde se cierra de forma inesperada, no se si sea un bug
o si ya esta reportada perdonen en si no es bug pero soy nuevo en este
mundo

-- 
*Juan C. Martínez Anaya*
* Ingeniero  civil*
"Se oyen pasos de alguien que no llega nunca "


systemsettings-20230129-141754.kcrash
Description: Binary data

Re: freezing / unstable Debian Testing on MSI Stealth GS77 laptop

[Martin Petersen]

Hi JD,

sorry to hear that you have these kind of troubles. I dont know much 
about this gpu/igpu setups, but I want to give some proceedings I would 
choose:


You write that there dont seem to be any logs.

Where did You look? I would expect, that there might me /var/log/syslog 
messages concerning kernel panics or maybe SystemD journal entries from 
that last boot (journalctl -b 1 or smth).


What kind of logs did You check or are some logs Your google searches 
might have produced not there or empty? They might have to bee enabled.


Also there might be error messages of the xserver /var/log/Xorg.0.log.

On top I would take a look into the messages of my Xsession itself 
(~.xsession-errors)	


Many places to check, I'm afraid to say :)

If You have another system You could ssh into Your crash prone laptop to 
get messages live.


Posting some details about the versions of the nvidia modules and such 
might be useful. Some other readers might be able to compare such strings.


And which CPU version does Your notebook have? (cat /proc/cpuinfo, 
maybe). If this is a CPU in a combo setup "some big/beefy cores and some 
lightweight/lowpower cores" it have implications w. applications in my 
opinion.


And one thing I would like to recommend: try another, maybe more recent 
system. Boot from a ubuntu or fedora or some outher fresh distributions 
live iso and check / compare modules and configuration parameters and - 
if possible - behaviour of the particular applications.


Good luck and please post log contents or snippes of logs, if You find some.

Cheers,

Martin


On 2023-01-25  09:56, JD wrote:

Hello,

I'm trying to find some help in order to debug or resolve the issues I'm 
facing. Hopefully, someone will be able to help me here.


The main problem that prevents me from trying to solve it myself is the 
absence of logs and messages.



So, my laptop MSI Stealth GS77 with a Debian testing (up to date) 
installed on it can freeze when launching 3D programs (both with setting 
the nVidia card or the integrated Intel chipset). Once it also 
complained about missing SSD drive (nvme). I currently don't know if 
both could be related, but I'd say it's unlikely.



Some information about my system:

I installed Debian testing since latest Debian stable had many issues 
(no audio, not wifi, unstable 3D graphics...). Debian stable with 
backports didn't helped much (it fixed some issues but not all). 
Therefore, the most practicable is Debian testing.



The issue I have is that seldom (but quite often), when running a 3D 
program, the OS is completely freezing. There is no way to retrieve any 
logs or information about the issue. The screen freezes, the keyboard 
doesn't respond. The only thing I can do is to use a long press on the 
power button to switch the laptop off (alt sys o doesn't work either). 
And on the next reboot, my filesystem fixes wrong inodes and therefore 
this is not possible to consultate any logs.



I don't really like to say that, but the laptop works well on Windows 11 
(no freeze, no crash, no nvme issues). Thus my belief that the issue is 
on the Linux side.



More information:

Desktop: XFCE

nvidia: latest proprietary modules available on Debian. Also tested with 
modules directly provided by nVidia.


3D programs run on nVidia or the Intel chipset (with setting 
appropriately __NV_PRIME_RENDER_OFFLOAD and __GLX_VENDOR_LIBRARY_NAME).


I played a lot with bumblebee, update-glx, keeping updating packages, 
but nothing worked at this time.



uname -a
Linux wormhole 6.1.0-1-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.4-1 
(2023-01-07) x86_64 GNU/Linux



lspci
00:00.0 Host bridge: Intel Corporation 12th Gen Core Processor Host 
Bridge/DRAM Registers (rev 02)
00:01.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI 
Express x16 Controller #1 (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-P 
Integrated Graphics Controller (rev 0c)
00:04.0 Signal processing controller: Intel Corporation Alder Lake 
Innovation Platform Framework Processor Participant (rev 02)
00:06.0 PCI bridge: Intel Corporation 12th Gen Core Processor PCI 
Express x4 Controller #0 (rev 02)
00:07.0 PCI bridge: Intel Corporation Alder Lake-P Thunderbolt 4 PCI 
Express Root Port #1 (rev 02)
00:08.0 System peripheral: Intel Corporation 12th Gen Core Processor 
Gaussian & Neural Accelerator (rev 02)
00:0d.0 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 USB 
Controller (rev 02)
00:0d.2 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI 
#0 (rev 02)
00:0d.3 USB controller: Intel Corporation Alder Lake-P Thunderbolt 4 NHI 
#1 (rev 02)
00:12.0 Serial controller: Intel Corporation Alder Lake-P Integrated 
Sensor Hub (rev 01)
00:14.0 USB controller: Intel Corporation Alder Lake PCH USB 3.2 xHCI 
Host Controller (rev 01)

00:14.2 RAM memory: Intel Corporation Alder Lake PCH Shared SRAM (rev 01)
00:14.3 Network controller: Intel Corporation Alder Lake-P PCH CNVi WiFi 

Re: laptop frozen when opening apps, debian testing with gnome

[rhkramer]

On Sunday, January 29, 2023 01:59:51 AM Shalom Ben-Zvii Kazaz wrote:
> There is no ssh when its frozen

Hmm, I'm a little confused, and maybe you are, also.

I think the intent of the advice was to log into the frozen laptop from 
another computer / device, using ssh *while the frozen laptop is not frozen*.

Further, on that other device, run a command like top or journalctrl -f, and 
then wait (or cause) the laptop to freeze.

Then examine top or such on the working computer to look for clues as to why 
the frozen laptop has frozen.

(I may be confused. ;-)

-- 
rhk 

(sig revised 20221206)

If you reply: snip, snip, and snip again; leave attributions; avoid HTML; 
avoid top posting; and keep it "on list".  (Oxford comma (and semi-colon) 
included at no charge.)  If you revise the topic, change the Subject: line.  
If you change the topic, start a new thread.

Writing is often meant for others to read and understand (legal documents 
excepted?) -- make it easier for your reader by various means, including 
liberal use of whitespace (short paragraphs, separated by whitespace / blank 
lines) and minimal use of (obscure?) jargon, abbreviations, acronyms, and 
references.

If someone has already responded to a question, decide whether any response 
you add will be helpful or not ...

A picture is worth a thousand words.  A video (or "audio"): not so much -- 
divide by 10 for each minute of video (or audio) or create a transcript and 
edit it to 10% of the original.

A speaker who uses ahhs, ums, or such may have a real physical or mental 
disability, or may be showing disrespect for his listeners by not properly 
preparing in advance and thinking before speaking.  (Remember Cicero who did 
not have enough time to write a short missive.)  (That speaker might have been 
"trained" to do this by being interrupted often if he pauses.)

A radio (or TV) station which broadcasts speakers with high pitched voices (or 
very low pitched / gravelly voices) (which older people might not be able to 
hear properly) disrespects its listeners.   Likewise if it broadcasts 
extraneous or disturbing sounds (like gunfire or crying), or broadcasts 
speakers using their native language (with or without an overdubbed 
translation).

A person who writes a sig this long probably has issues and disrespects (and 
offends) a large number of readers. ;-)
'

Re: Bookworm 1/28/23 updates - No Audio Devices Found

[Brad Rogers]

On Sun, 29 Jan 2023 12:11:33 -0500
Timothy M Butterworth  wrote:

Hello Timothy,

>I did not try a new user. I did try deleting "~/.config/pulseaudio"

Sorry to say, I've reached the limit of my knowledge on the subject.
:-(

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
All these things are mine!
Money is Not Our God -  Killing Joke


pgpcVPMwvALzC.pgp
Description: OpenPGP digital signature

Re: Broken IPv6 / IPv4 configuration, or Gmail brokenness?

[Celejar]

On Sat, 28 Jan 2023 20:55:18 +
Andy Smith  wrote:

> Hi,
> 
> On Sun, Jan 22, 2023 at 11:42:18PM -0500, Celejar wrote:
> > Shouldn't this be included somewhere prominently in the Debian
> > documentation, in the form of a Big Fat Warning that the standard
> > dual-stack condiguration used by Debian can cause serious breakage if
> > one's ISP doesn't support IPv6?
> 
> Not having IPv6 is not the problem. As you discovered later in this
> thread, your ISP is providing just enough IPv6 for your router to
> think it has a v6 block to hand out, but not enough that it actually
> works. It's a misconfiguration by your ISP and not something that
> any operating system's documentation needs to point out. They could
> also let you connect to them but make IPv4 not work, it's just that
> you'd notice that very quickly!

Understood. There's apparently even a quasi-official name for this:
"IPv6 brokenness":

https://en.wikipedia.org/wiki/IPv6_brokenness_and_DNS_whitelisting

> In the field of IPv6 deployment, IPv6 brokenness was bad behavior seen
> in early tunneled or dual stack IPv6 deployments where unreliable or
> bogus IPv6 connectivity is chosen in preference to working IPv4
> connectivity. This often resulted in long delays in web page loading,
> where the user had to wait for each attempted IPv6 connection to time
> out before the IPv4 connection was tried. These timeouts ranged from
> being near-instantaneous in the best cases, to taking anywhere between
> four seconds to three minutes.

The article proceeds to assure the reader that:

> IPv6 brokenness is now generally regarded as a solved problem for
> almost all practical purposes, following improvements at both the
> transport and application layers.

But I guess I've managed to encounter a "practical" instance of
current IPv6 brokenness :|

...

> Anyway, if the ISP can't fix the IPv6 and can't be convinced to stop
> advertising it even when it doesn't work, I think you'd be best


Makes sense - I think I've seen other users of my ISP stating in online
forums that that's what they had to do at some point.

> off trying to disable radvd on the router. Failing that, disabling
> IPv6 on all your clients (check your phones too, as they will try

Thank you.

-- 
Celejar

Re: Bookworm 1/28/23 updates - No Audio Devices Found

[Timothy M Butterworth]

On Sun, Jan 29, 2023 at 12:11 PM Timothy M Butterworth <
timothy.m.butterwo...@gmail.com> wrote:

>
>
> On Sun, Jan 29, 2023 at 7:55 AM Brad Rogers  wrote:
>
>> On Sun, 29 Jan 2023 07:22:02 -0500
>> Timothy M Butterworth  wrote:
>>
>> Hello Timothy,
>>
>> >I upgraded to 5.27beta so far no new issues. I just installed Wayland
>>
>> Good to know.  Thanks for the info.
>>
>> >so I can try it out. My sound cards are still not working though.
>>
>> Have you tried;
>>
>> (a) checking volume levels
>> because sometimes things get 'fiddled with' on update.
>>
>
> It is not a volume or a mute problem. KDE does not register any sound
> cards being installed. The hardware has drivers and it is installed. I can
> see the hardware with aplay.
>
> aplay -l
>  List of PLAYBACK Hardware Devices 
> card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
> card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [SAMSUNG]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
> card 1: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287
> Analog]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
> card 2: H540 [Logitech USB Headset H540], device 0: USB Audio [USB Audio]
>  Subdevices: 1/1
>  Subdevice #0: subdevice #0
>
> (b) with a new user
>> to try and ascertain whether it's unique to your usual
>> user or an across the board problem.
>>
>
> I did not try a new user. I did try deleting "~/.config/pulseaudio"
>

I tried creating a new user, it still has the same problem.


> --
>>  Regards  _   "Valid sig separator is {dash}{dash}{space}"
>>  / )  "The blindingly obvious is never immediately apparent"
>> / _)rad   "Is it only me that has a working delete key?"
>> Success defined by acquisition stinks
>> Money is Not Our God -  Killing Joke
>>
>
>
> --
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: Bookworm 1/28/23 updates - No Audio Devices Found

[Timothy M Butterworth]

On Sun, Jan 29, 2023 at 7:55 AM Brad Rogers  wrote:

> On Sun, 29 Jan 2023 07:22:02 -0500
> Timothy M Butterworth  wrote:
>
> Hello Timothy,
>
> >I upgraded to 5.27beta so far no new issues. I just installed Wayland
>
> Good to know.  Thanks for the info.
>
> >so I can try it out. My sound cards are still not working though.
>
> Have you tried;
>
> (a) checking volume levels
> because sometimes things get 'fiddled with' on update.
>

It is not a volume or a mute problem. KDE does not register any sound cards
being installed. The hardware has drivers and it is installed. I can see
the hardware with aplay.

aplay -l
 List of PLAYBACK Hardware Devices 
card 0: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 0: Generic [HD-Audio Generic], device 7: HDMI 1 [SAMSUNG]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 1: Generic_1 [HD-Audio Generic], device 0: ALC287 Analog [ALC287
Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
card 2: H540 [Logitech USB Headset H540], device 0: USB Audio [USB Audio]
 Subdevices: 1/1
 Subdevice #0: subdevice #0

(b) with a new user
> to try and ascertain whether it's unique to your usual
> user or an across the board problem.
>

I did not try a new user. I did try deleting "~/.config/pulseaudio"


> --
>  Regards  _   "Valid sig separator is {dash}{dash}{space}"
>  / )  "The blindingly obvious is never immediately apparent"
> / _)rad   "Is it only me that has a working delete key?"
> Success defined by acquisition stinks
> Money is Not Our God -  Killing Joke
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: computer not starting from usb since installation

[Andrew M.A. Cater]

On Sat, Jan 28, 2023 at 01:10:47PM +0300, Semih Ozlem wrote:
> Since I installed debian 11 my computer no longer boots from usbs even if
> at startup from boot menu I choose to start from a live usb. Can this be
> changed by editing grub and if so how?
> 
> Thank you
> 
> Semih

Hi Semih,

Are there any logs / any indication in dmesg if you put a USB device into
a port?

When you installed Debian 11, did you choose to put all possible devices
into the initramfs or just the ones for this computer?

What else has changed? :)

All the very best, as ever,

Andy Cater

Re: (deb-cat) Firefox ESR: out of memory

[Narcis Garcia]

En un altre ordinador, actualitzar firefox-esr a la versió 102.7 no ha 
resolt el problema, així que l'he hagut de tornar a la versió 
91.13.0esr-1~deb11u1


Salut.


El 19/1/23 a les 7:50, Narcis Garcia ha escrit:
En un dels ordinadors afectats he actualitzat paquets, amb firefox-esr 
102.7

L'aplicació de moment funciona, així que potser el problema estigui resolt.

Salut.


El 21/11/22 a les 18:18, Narcis Garcia ha escrit:
En aquest altre ordinador que esmentava, acabo d'actualitzar a 
M.Firefox 102.5 i ara sí que peta. Però el missatge per terminal és 
diferent:


Exiting due to channel error.

I veig que no puc desactuaitzar a la v102.4 perquè no hi és en 
repositoris. Si desactualitzo, ha de ser a la 91.13



El 17/11/22 a les 13:05, Narcis Garcia ha escrit:
En el «safe-mode» la v102.x funciona bé, la qual cosa inclou la 
desactivació de tots els complements.
Però si desactivo complements manualment, sense el «safe-mode» es 
reprodueix el problema en aquest ordinador.


Si fos el cas que algun complement fos problemàtic, tampoc no 
l'aconsegueixo identificar. En un altre ordinador amb Debian Stable 
(11) també hi corre el M.Firefox 102.4 amb els mateixos complements, 
i sense problema.

Suposo que hauré d'esperar la versió 115 per aquest ordinador.


El 17/11/22 a les 10:30, Josep Lladonosa ha escrit:
Has provat de desactivar complements, aviam si és un d'ells el que 
falla?




El dc., 16 de nov. 2022, 20:47, Narcis Garcia > va escriure:


    Bones,

    Aquest matí en una Debian Stable (11) he actualitzat paquets i 
s'hi ha

    posat el M.Firefox versió 102.4
    (Abans ja hi havia la versió 102.x)

    En iniciar M.Firefox, incondicionalment ha tingut aquest 
comportament:

    1. Comença a menjar memòria fins a més de 20GiB
    2. En menys d'un minut dóna aquest missatge per Terminal i es queda
    bloquejat:
    [unhandlable oom] Failed to mmap, likely no more mappings available
    ./memory/build/mozjemalloc.cpp : 1398ExceptionHandler::GenerateDump
    cloned child 501530
    ExceptionHandler::SendContinueSignalToChild sent continue signal to
    child
    ExceptionHandler::WaitForContinueSignal waiting for continue 
signal...


    Ara per la tarda he tornat a actualitzar paquets, i ha arribat la
    versió
    102.5 de M.Firefox.
    Ara la cosa és més resolutiva i escueta:
    1. Comença a menjar memòria fins a poc menys de 20GiB
    2. En menys de 20 segons dóna aquest missatge per Terminal i 
finalitza

    amb codi de sortida 11:
    out of memory: 0x00018810 bytes requested

    En un segon intent, el missatge és més llarg:
    [unhandlable oom] Failed to mmap, likely no more mappings available
    ./memory/build/mozjemalloc.cpp : 1398

    I en un tercer intent, el problema es reprodueix igual que abans,
    quedant bloquejat:
    [unhandlable oom] Failed to mmap, likely no more mappings available
    ./memory/build/mozjemalloc.cpp : 1398ExceptionHandler::GenerateDump
    cloned child 2065098
    ExceptionHandler::SendContinueSignalToChild sent continue signal to
    child
    ExceptionHandler::WaitForContinueSignal waiting for continue 
signal...



    Per a sortir del pas, he desactualitzat el M.Firefox a la versió
    91.13 ,
    que em funciona bé. Per a què s'empassi el perfil més modern, he 
hagut

    d'apartar-ne el fitxer compatibility.ini

    --
    Narcis Garcia

    __
    I'm using this dedicated address because personal addresses aren't
    masked enough at this mail public archive. Public archive 
administrator

    should fix this against automated addresses collectors.









--


__
I'm using this express-made address because personal addresses aren't
masked enough at this mail public archive. Public archive administrator
should fix this against automated addresses collectors.

Re: Bookworm 1/28/23 updates - No Audio Devices Found

[Brad Rogers]

On Sun, 29 Jan 2023 07:22:02 -0500
Timothy M Butterworth  wrote:

Hello Timothy,

>I upgraded to 5.27beta so far no new issues. I just installed Wayland

Good to know.  Thanks for the info.

>so I can try it out. My sound cards are still not working though.

Have you tried;

(a) checking volume levels
because sometimes things get 'fiddled with' on update.

(b) with a new user
to try and ascertain whether it's unique to your usual
user or an across the board problem.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
Success defined by acquisition stinks
Money is Not Our God -  Killing Joke


pgpdNPZcrEvD0.pgp
Description: OpenPGP digital signature

Re: Bookworm 1/28/23 updates - No Audio Devices Found

[Timothy M Butterworth]

On Sun, Jan 29, 2023 at 5:19 AM Brad Rogers  wrote:

> On Sat, 28 Jan 2023 10:41:38 -0500
> Timothy M Butterworth  wrote:
>
> Hello Timothy,
>
> >I am looking forward to 5.27beta! It has a lot of good improvements.
>
> As I suggested, the migration to testing has started today.  I'm holding
> off for a few days to be sure (well, as sure as I can be) that
> everything necessary for a smooth upgrade has migrated.
>

I upgraded to 5.27beta so far no new issues. I just installed Wayland so I
can try it out. My sound cards are still not working though.


> --
>  Regards  _   "Valid sig separator is {dash}{dash}{space}"
>  / )  "The blindingly obvious is never immediately apparent"
> / _)rad   "Is it only me that has a working delete key?"
> I ain't got no time for intellectual music, e.g. Hergest Ridge
> Heads Down No Nonsense Mindless Boogie - Alberto y Lost Trios Paranoias
>


-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀

Re: Bookworm 1/28/23 updates - No Audio Devices Found

[Brad Rogers]

On Sat, 28 Jan 2023 10:41:38 -0500
Timothy M Butterworth  wrote:

Hello Timothy,

>I am looking forward to 5.27beta! It has a lot of good improvements.

As I suggested, the migration to testing has started today.  I'm holding
off for a few days to be sure (well, as sure as I can be) that
everything necessary for a smooth upgrade has migrated.

-- 
 Regards  _   "Valid sig separator is {dash}{dash}{space}"
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
I ain't got no time for intellectual music, e.g. Hergest Ridge
Heads Down No Nonsense Mindless Boogie - Alberto y Lost Trios Paranoias


pgpXNRkgfbFlP.pgp
Description: OpenPGP digital signature