Back again. This time I have no sound and I have no totem. Supposedly I have pipewire. vlc runs, but no sound.
I've got this: $ systemctl --user status wireplumber â wireplumber.service - Multimedia Service Session Manager Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor> Active: active (running) since Sat 2022-06-25 16:09:28 CDT; 2 weeks 1 day > Main PID: 1668 (wireplumber) Tasks: 4 (limit: 9388) Memory: 6.4M CPU: 3.432s CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wirepl> ââ 1668 /usr/bin/wireplumber
Jun 25 16:09:28 2001-48F8-3004-2CE-0-0-0-D5CE-dynamic.midco.net systemd[1423]: > Jun 25 16:09:29 2001-48F8-3004-2CE-0-0-0-D5CE-dynamic.midco.net wireplumber[166> $
When totem dies, I get this from dmesg: 00007ffe669b06e8 error 15 in libGLX.so.0.0.0[7f230dd1a000+3000] [1303407.845470] Code: 00 00 08 00 00 00 00 00 00 00 19 d2 01 00 00 00 00 00 f8 0a 02 00 00 00 00 00 08 00 00 00 00 00 00 00 60 ac 01 00 00 00 00 00 <00> 0b 02 00 00 00 00 00 08 00 00 00 00 00 00 00 29 d2 01 00 00 00 [1303478.855160] totem[585380]: segfault at 7f2067062090 ip 00007f2067062090 sp 00007ffc13420858 error 15 in libGLX.so.0.0.0[7f2067062000+3000] [1303478.855178] Code: 00 00 88 28 00 00 00 00 00 00 00 10 00 00 00 00 00 00 01 00 00 00 05 00 00 00 00 30 00 00 00 00 00 00 00 30 00 00 00 00 00 00 <00> 30 00 00 00 00 00 00 3d 9f 01 00 00 00 00 00 3d 9f 01 00 00 00 [1304507.408590] totem[585489]: segfault at 7fa866483090 ip 00007fa866483090 sp 00007ffda3a6b868 error 15 in libGLX.so.0.0.0[7fa866483000+3000] [1304507.408609] Code: 00 00 88 28 00 00 00 00 00 00 00 10 00 00 00 00 00 00 01 00 00 00 05 00 00 00 00 30 00 00 00 00 00 00 00 30 00 00 00 00 00 00 <00> 30 00 00 00 00 00 00 3d 9f 01 00 00 00 00 00 3d 9f 01 00 00 00
I'm running F35 and Gnome. I can run the speaker tests, the speaker icons actually appear this time, but I get no sound. If I play with the pale green connector in back of the PC, I get the expected scratchy sound.
Now what?
On 7/10/22 17:07, Michael Hennebry wrote:
Back again. This time I have no sound and I have no totem. Supposedly I have pipewire. vlc runs, but no sound.
I've got this: $ systemctl --user status wireplumber â wireplumber.service - Multimedia Service Session Manager Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; vendor> Active: active (running) since Sat 2022-06-25 16:09:28 CDT; 2 weeks 1 day > Main PID: 1668 (wireplumber) Tasks: 4 (limit: 9388) Memory: 6.4M CPU: 3.432s CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wirepl> ââ 1668 /usr/bin/wireplumber
Jun 25 16:09:28 2001-48F8-3004-2CE-0-0-0-D5CE-dynamic.midco.net systemd[1423]: > Jun 25 16:09:29 2001-48F8-3004-2CE-0-0-0-D5CE-dynamic.midco.net wireplumber[166> $
When totem dies, I get this from dmesg: 00007ffe669b06e8 error 15 in libGLX.so.0.0.0[7f230dd1a000+3000] [1303407.845470] Code: 00 00 08 00 00 00 00 00 00 00 19 d2 01 00 00 00 00 00 f8 0a 02 00 00 00 00 00 08 00 00 00 00 00 00 00 60 ac 01 00 00 00 00 00 <00> 0b 02 00 00 00 00 00 08 00 00 00 00 00 00 00 29 d2 01 00 00 00 [1303478.855160] totem[585380]: segfault at 7f2067062090 ip 00007f2067062090 sp 00007ffc13420858 error 15 in libGLX.so.0.0.0[7f2067062000+3000] [1303478.855178] Code: 00 00 88 28 00 00 00 00 00 00 00 10 00 00 00 00 00 00 01 00 00 00 05 00 00 00 00 30 00 00 00 00 00 00 00 30 00 00 00 00 00 00 <00> 30 00 00 00 00 00 00 3d 9f 01 00 00 00 00 00 3d 9f 01 00 00 00 [1304507.408590] totem[585489]: segfault at 7fa866483090 ip 00007fa866483090 sp 00007ffda3a6b868 error 15 in libGLX.so.0.0.0[7fa866483000+3000] [1304507.408609] Code: 00 00 88 28 00 00 00 00 00 00 00 10 00 00 00 00 00 00 01 00 00 00 05 00 00 00 00 30 00 00 00 00 00 00 00 30 00 00 00 00 00 00 <00> 30 00 00 00 00 00 00 3d 9f 01 00 00 00 00 00 3d 9f 01 00 00 00
I'm running F35 and Gnome. I can run the speaker tests, the speaker icons actually appear this time, but I get no sound. If I play with the pale green connector in back of the PC, I get the expected scratchy sound.
Now what?
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
I suppose I should try it. I'll do it when I'm a bit more awake.
On 7/10/22 21:53, Michael Hennebry wrote:
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
I suppose I should try it. I'll do it when I'm a bit more awake.
The command is reboot
On 7/10/22 22:04, ToddAndMargo via users wrote:
On 7/10/22 21:53, Michael Hennebry wrote:
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
I suppose I should try it. I'll do it when I'm a bit more awake.
The command is reboot
There are two other things that can cause your symptoms:
1) lose audio connections or connection in the wrong holes (the 3.5 mm goes into the green hole).
2) your CPU is extremely busy. Check it out with something like atop or htop.
-T
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
Thanks. I have sound now.
I often have rather a lot of files open. I won't do a killall gvim until I've ascertained that none need saving. I won't do the reboot until important external media have been removed. When I'm already having trouble, I prefer not to rely too much on how things are supposed to handle their death throes.
BTW I'd thought reinstalling was the Windows cure-all.
On Mon, 2022-07-11 at 09:09 -0500, Michael Hennebry wrote:
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
Thanks. I have sound now.
I often have rather a lot of files open. I won't do a killall gvim until I've ascertained that none need saving. I won't do the reboot until important external media have been removed. When I'm already having trouble, I prefer not to rely too much on how things are supposed to handle their death throes.
BTW I'd thought reinstalling was the Windows cure-all.
Rebooting, not reinstalling.
poc
Michael Hennebry:
BTW I'd thought reinstalling was the Windows cure-all.
Patrick O'Callaghan:
Rebooting, not reinstalling.
Reboot, re-install, return for refund.
Each of them gives you a headache
On 7/11/22 08:44, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 09:09 -0500, Michael Hennebry wrote:
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
Thanks. I have sound now.
I often have rather a lot of files open. I won't do a killall gvim until I've ascertained that none need saving. I won't do the reboot until important external media have been removed. When I'm already having trouble, I prefer not to rely too much on how things are supposed to handle their death throes.
BTW I'd thought reinstalling was the Windows cure-all.
Rebooting, not reinstalling.
It is worse than you think. One of the unethical things M$ does is called Fast Boot (Fast Startup). Basically when you think you have shutdown, you have only exited your programs and suspended. So when you, haha, power back up, "Look see how fast it boots!" and you get back all of the sins of the past.
Windows goes a bit nuts after running for three days or so, so your nightly shutdown keeps you clean, unless you have Fast Boot in effect, which M$ does by default.
And to make matters work, you have to throw a shutdown /r /f /t 00
after turning the bugger off or the setting change does not take.
I have fixed tons of Windows machines this way. Sometimes I have had the pull the power plug first as nothing would respond.
You guys do not know the drama you are missing by running Fedora!
-T
I always wondered about that "reinstall the software" thing.
I mean, how much should I trust software from someone who apparently is unable to just copy the software onto the disk?
And even worse, it actually works sometimes.
On Mon, 2022-07-11 at 11:21 -0700, ToddAndMargo via users wrote:
On 7/11/22 08:44, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 09:09 -0500, Michael Hennebry wrote:
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
Thanks. I have sound now.
I often have rather a lot of files open. I won't do a killall gvim until I've ascertained that none need saving. I won't do the reboot until important external media have been removed. When I'm already having trouble, I prefer not to rely too much on how things are supposed to handle their death throes.
BTW I'd thought reinstalling was the Windows cure-all.
Rebooting, not reinstalling.
In case it wasn't obvious, I was merely pointing that Michael had misread the previous post, which mentioned rebooting, not reinstalling. That's all.
It is worse than you think. One of the unethical things M$ does is called Fast Boot (Fast Startup). Basically when you think you have shutdown, you have only exited your programs and suspended. So when you, haha, power back up, "Look see how fast it boots!" and you get back all of the sins of the past.
So basically hibernation. I'm not fan of MS, but isn't it a bit of a stretch to call it "unethical"?
poc
On 7/11/22 14:28, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 11:21 -0700, ToddAndMargo via users wrote:
On 7/11/22 08:44, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 09:09 -0500, Michael Hennebry wrote:
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
Thanks. I have sound now.
I often have rather a lot of files open. I won't do a killall gvim until I've ascertained that none need saving. I won't do the reboot until important external media have been removed. When I'm already having trouble, I prefer not to rely too much on how things are supposed to handle their death throes.
BTW I'd thought reinstalling was the Windows cure-all.
Rebooting, not reinstalling.
In case it wasn't obvious, I was merely pointing that Michael had misread the previous post, which mentioned rebooting, not reinstalling. That's all.
It is worse than you think. One of the unethical things M$ does is called Fast Boot (Fast Startup). Basically when you think you have shutdown, you have only exited your programs and suspended. So when you, haha, power back up, "Look see how fast it boots!" and you get back all of the sins of the past.
So basically hibernation. I'm not fan of MS, but isn't it a bit of a stretch to call it "unethical"?
poc
No stretch at all. Shutdown means to shutdown, not to hibernate/suspend. M$ is lying to its customers so they can brag about how fast their stuff boots.
On Mon, Jul 11, 2022 at 7:36 PM ToddAndMargo via users < users@lists.fedoraproject.org> wrote:
On 7/11/22 14:28, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 11:21 -0700, ToddAndMargo via users wrote:
On 7/11/22 08:44, Patrick O'Callaghan wrote:
[...]
It is worse than you think. One of the unethical things M$ does is called Fast Boot (Fast Startup). Basically when you think you have shutdown, you have only exited your programs and suspended. So when you, haha, power back up, "Look see how fast it boots!" and you get back all of the sins of the past.
So basically hibernation. I'm not fan of MS, but isn't it a bit of a stretch to call it "unethical"?
poc
No stretch at all. Shutdown means to shutdown, not to hibernate/suspend. M$ is lying to its customers so they can brag about how fast their stuff boots.
Maybe not lying, just MS is so big they can get away with redefining technical terms.
Clear, consistent, use of technical terms is important. Now shutdown means something different for many Windows systems. Abuse of terminology adds to the confusion many people for whom English is a second language already have with the lack of consistency in English.
On 7/11/22 17:55, George N. White III wrote:
On Mon, Jul 11, 2022 at 7:36 PM ToddAndMargo via users <users@lists.fedoraproject.org mailto:users@lists.fedoraproject.org> wrote:
On 7/11/22 14:28, Patrick O'Callaghan wrote: > On Mon, 2022-07-11 at 11:21 -0700, ToddAndMargo via users wrote: >> On 7/11/22 08:44, Patrick O'Callaghan wrote: > [...] > >> It is worse than you think. One of the unethical things >> M$ does is called Fast Boot (Fast Startup). Basically >> when you think you have shutdown, you have only exited >> your programs and suspended. So when you, haha, power >> back up, "Look see how fast it boots!" and you get >> back all of the sins of the past. > > So basically hibernation. I'm not fan of MS, but isn't it a bit of a > stretch to call it "unethical"? > > poc No stretch at all. Shutdown means to shutdown, not to hibernate/suspend. M$ is lying to its customers so they can brag about how fast their stuff boots.Maybe not lying, just MS is so big they can get away with redefining technical terms.
Clear, consistent, use of technical terms is important. Now shutdown means something different for many Windows systems. Abuse of terminology adds to the confusion many people for whom English is a second language already have with the lack of consistency in English.
Hi George,
In this case, it is deliberate.
-T
On Mon, 2022-07-11 at 14:33 -0400, Tom Horsley wrote:
I always wondered about that "reinstall the software" thing.
I mean, how much should I trust software from someone who apparently is unable to just copy the software onto the disk?
And even worse, it actually works sometimes.
I'd come to a few conclusions regarding that:
Silent disk errors. Things disappeared without notice while writing, and/or later on. And checkdisk was fond of just deleting files it considered faulty.
Mangling of files read from disk. When you open a file, a file system can record when the file was last accessed. So what happens when it pokes the data on a file and has a crash? Can it destroy the file? (We're talking self-destructive MS file systems, here.) Why else should some .dll file disappear that *you* never had interaction with.
Race conditions. Some programming flaw got in the way of some write during installation, that didn't happen during the re-installation. Although that doesn't take into account things that worked, later failed, then got fixed by a reinstall.
On Tue, Jul 12, 2022 at 2:24 AM Tim via users users@lists.fedoraproject.org wrote:
On Mon, 2022-07-11 at 14:33 -0400, Tom Horsley wrote:
I always wondered about that "reinstall the software" thing.
I mean, how much should I trust software from someone who apparently is unable to just copy the software onto the disk?
And even worse, it actually works sometimes.
I use a very large and complex app with a Java GUI and heavy lifting done by open source libraries for a huge range of file formats, GDAL, and various numerical libraries. There are silent background downloads of "ancillary" files. Reinstalling is often needed when it breaks -- probably due to a corrupt file. There are versions for Linux, macOS, and Windows, but I don't see any difference across platforms so pretty sure there are glitches writing configuration files.
I'd come to a few conclusions regarding that:
Silent disk errors. Things disappeared without notice while writing, and/or later on. And checkdisk was fond of just deleting files it considered faulty.
Mangling of files read from disk. When you open a file, a file system can record when the file was last accessed. So what happens when it pokes the data on a file and has a crash? Can it destroy the file? (We're talking self-destructive MS file systems, here.) Why else should some .dll file disappear that *you* never had interaction with.
Race conditions. Some programming flaw got in the way of some write during installation, that didn't happen during the re-installation. Although that doesn't take into account things that worked, later failed, then got fixed by a reinstall.
I've seen many cases where users had started some GUI app from the shell then done <Ctrl-Z> in case they might want to come back to it, but end up leaving it suspended for days. Then they try to install an update and the problems begin.
On Mon, 11 Jul 2022, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 11:21 -0700, ToddAndMargo via users wrote:
On 7/11/22 08:44, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 09:09 -0500, Michael Hennebry wrote:
On Sun, 10 Jul 2022, ToddAndMargo via users wrote:
Not to ask too stupid a question, but I notice problems like these after I do a `dnf upgrade`. Have you tried the universal Windows cure-all solutions and rebooted your computer?
Thanks. I have sound now.
BTW I'd thought reinstalling was the Windows cure-all.
Rebooting, not reinstalling.
On Mon, 11 Jul 2022, Patrick O'Callaghan wrote:
On Mon, 2022-07-11 at 11:21 -0700, ToddAndMargo via users wrote: In case it wasn't obvious, I was merely pointing that Michael had misread the previous post, which mentioned rebooting, not reinstalling. That's all.
I'd read it correctly, just was not at all the sure it was correct. To be clear, by "reinstall", I meant reinstall Windows.
Rebooting is ordinary enough that I should have tried it without prompting. That said, I do not know what when wrong in the first place, so do not know how to avoid it.
-
George N. White III -
Joe Zeff -
Michael Hennebry -
Patrick O'Callaghan -
Tim -
ToddAndMargo -
Tom Horsley