| [01:31] <IrcsomeBot1> g_padua was added by: g_padua | |
| [01:35] <IrcsomeBot1> <g_padua> Hello friends … I forgot my root password and can't access the computer. Already tried to hold Shift in the initialization, but no good, Grub does not shows up. | |
| [02:01] <IrcsomeBot1> <YesEyeCan> @TJ Wolf, Do you have any additional drives active? I'm not sure why but this problem has been popping up lately | |
| [02:28] <IrcsomeBot1> Giao Linh was added by: Giao Linh | |
| [03:25] <brae> is this server still active? | |
| [03:29] <IrcsomeBot1> <YesEyeCan> Yea | |
| [03:46] <brae> any of you using zorin os | |
| [03:47] <brae> ubuntu? | |
| === Guest71528 is now known as rajm | |
| [10:20] <MrSassyPants> diogenes_, yes, sddm starts X. But how do I fix the issue? I guess I have to edit a config file so sddm is started later? | |
| [10:25] <diogenes_> MrSassyPants, you can set the service to start after another specific service has started, it's systemd. | |
| [10:27] <MrSassyPants> even adding the driver module to the modules.conf equivalent doesn't seem to make sure the sound device is loaded before sddm causes the system to tally sound drivers | |
| [10:28] <MrSassyPants> could be wrong on the causality here, all I know is that if I log out and back in, the sound device appears, but if I plain kill X to force a reset, it doesn't. | |
| [10:29] <MrSassyPants> anyone know whats happening there? | |
| [10:30] <MrSassyPants> the sound device would be snd_hda_intel , and until I logged out and back in again, the kde sound system only recognizes spdif, not normal line out | |
| [10:30] <diogenes_> systemctl list-units | grep -i aud | |
| [10:31] <IrcsomeBot1> Kaiser LEONA was added by: Kaiser LEONA | |
| [10:31] <MrSassyPants> loaded active plugged for the matching driver (right now only spdif is displayed in kde) | |
| [10:31] <IrcsomeBot1> <Kaiser LEONA> (Photo, 515x738) https://irc-attachments.kde.org/NvNoLQvo/file_39101.jpg | |
| [10:40] <MrSassyPants> Oh. just killing pulseaudio actually fixes it. This seems to be a pulseaudio problem | |
| [11:17] <Mamarok> MrSassyPants: that's weird, sounds like a bug | |
| [11:26] <MrSassyPants> pulseaudio guys suspect it's pipewire | |
| [11:26] <MrSassyPants> how do I properly stop pipewire from being started without breaking things for good | |
| [11:26] <MrSassyPants> so I can test this | |
| [11:33] <MrSassyPants> I failed at "disabling" pipewire with systemctl, but apt-removing it has fixed the issue. Take note. | |
| [11:35] <MrSassyPants> pulseaudio guys request I get this up with kubuntu devs | |
| [11:36] <MrSassyPants> They say the issue would be fixed with versions >= 0.3.13 of pipewire | |
| [11:36] <Mamarok> yes, as I said, this sounds like a bug | |
| [11:36] <MrSassyPants> anyhow, the version that I have in the repo right now (and has caused this problem) is 0.3.10-4 | |
| [11:37] <Mamarok> funnily enough I have the same version, but not your problems | |
| [11:37] <MrSassyPants> So this may happen to more people | |
| [11:37] <MrSassyPants> yeah, it's basically a race condition where pipewire accesses the soundcard and locks it briefly and this just happens to coincide with when pulseaudio is doing the same | |
| [11:38] <MrSassyPants> and then pulseaudio can't tally the sound device | |
| [11:38] <Mamarok> What I don't understand is why pipewire is needed in the first place | |
| [11:38] <MrSassyPants> a simple pulseaudio -k fixes it | |
| [11:38] <MrSassyPants> I have no idea, I have apt removed it and everything seems to be fine. | |
| [11:39] <Mamarok> makes jsut one more sound server potentially causing havoc | |
| [11:39] <Mamarok> and sound already is a tricky beast | |
| [11:41] <MrSassyPants> I'm not sure it's part of the standard kubuntu install, I may have installed it as a dependency of a dependency of a gnome-centric thing | |
| [11:42] <Mamarok> it is nbeeded if you use Wayland instead of X | |
| [11:42] <MrSassyPants> I am running Xorg though | |
| [11:42] <Mamarok> that's why it is automatically installed | |
| [11:43] <Mamarok> so you don't need it, at least not for now | |
| [11:43] <MrSassyPants> well, make sure you get >= 0.3.13 into the repo | |
| [11:43] <MrSassyPants> asap. This problem only popped up a few days ago | |
| [11:43] <Mamarok> where did you report this? because you are talking about talking with other people, but did you report this as a bug to Kubuntu? | |
| [11:44] <MrSassyPants> I did not report this as a bug to kubuntu | |
| [11:44] <Mamarok> please do | |
| [11:44] <MrSassyPants> I talked to the pulseaudio guys | |
| [11:44] <Mamarok> because you want it to be changed in Kubuntu, so you need to report it | |
| [11:44] <MrSassyPants> I don't do bug reports. bug report related PTSD. I'm just verbally informing you | |
| [11:45] <Mamarok> which means it will disappear in Nirvana | |
| [11:45] <Mamarok> bug reports are important | |
| [11:45] <Mamarok> becuaase you are hit by a race condition that might not hit other people | |
| [11:45] <Mamarok> so unless it is reported there is no paper trail of it | |
| [11:46] <MrSassyPants> yeah, this version of pipewire has been installed for 3 weeks, but it only started happening this week after I did a (possibly completely unrelated) update | |
| [11:47] <Mamarok> I don't even know the original problem you were hit with, not in my timeline here | |
| [11:47] <MrSassyPants> the update may have changed the exact timings at which pulseaudio and pipewire do their things | |
| [11:47] <Mamarok> IRC is definitely the wrong place to report this | |
| [11:47] <Mamarok> we need a bug report that sums up the problem | |
| [11:47] <MrSassyPants> Oh. Booting the system causes the sound device to be recognized incorrectly in the kde sound thingy | |
| [11:47] <Mamarok> again, please report this | |
| [11:48] <MrSassyPants> I at first thought the problem was SDDM related (SDDM starting too early before sound devices are fully initialized) but then noticed a simple pulseaudio -k fixes it | |
| [11:49] <MrSassyPants> so I dug into pulseaudio and they immediately named pipewire as a suspect, I confirmed that it was running and that removing it resolved the problem (of sound devices not being fully available after booting, until i kill the pulseaudio server) | |
| [11:49] <Mamarok> you do realise that I am not a developer, the Kubuntu devss might not be around in this channel right now and you repeating the issue might again go to Nirvana? | |
| [11:49] <Mamarok> BG Report, Please! | |
| [11:49] <Mamarok> s/BG/Bug/ | |
| [11:51] <MrSassyPants> https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1897965 already exists | |
| [11:51] <ubottu> Launchpad bug 1897965 in pipewire (Ubuntu) "PulseAudio doesn't work when pipewire is installed (ie. KDE)" [Medium,Triaged] | |
| [11:51] <Mamarok> please add more information there, then | |
| [11:56] <Mamarok> you said: <MrSassyPants> They say the issue would be fixed with versions >= 0.3.13 of pipewire" who is "They"? | |
| [11:56] <MrSassyPants> pulseaudio devs | |
| [11:56] <Mamarok> ok, might be a good idea to add this to the bug reprt | |
| [11:57] <MrSassyPants> don't worry | |
| [12:04] <MrSassyPants> posted | |
| [12:05] <vdr_> deepweb | |
| [13:03] <BluesKaj> Hi folks | |
| [13:55] <IrcsomeBot1> <g_padua> @g_padua, Can someone help me? | |
| [13:55] <BluesKaj> @g_padua, just ask your question | |
| [14:20] <IrcsomeBot1> <g_padua> I cannot access Grub through pressing any keys on initialization. Forgot my root password and can't login. | |
| [14:22] <BluesKaj> black screen? | |
| [14:26] <IrcsomeBot1> <g_padua> The Kubuntu logo appears. And some "log scrolling", "command lines", if I keep pressing Esc, or E. By pressing Pause/Power it slows down. But cannot interact. | |
| [14:27] <BluesKaj> ctl+c | |
| [14:28] <BluesKaj> I assume this is a new kubuntu installation ? | |
| [14:38] <IrcsomeBot1> <g_padua> It's not new. Ctrl+C doesn't go either. | |
| === dilfridge is now known as TinkyWinky | |
| === TinkyWinky is now known as dilfridge | |
| [15:59] <IrcsomeBot1> <Giao Linh> used to work fine | |
| [16:04] <IrcsomeBot1> <E A> Kde kuralım dedik ama herkes İngilizce yazıyor. Hadi bana güle güle 😉 | |
| [16:04] <TomTom> I updated from 20.04. to 20.10. but pulseaudio has now a problem. I have to kill (`pulseaudio -k`) and restart it after each login to get sound. | |
| [16:04] <TomTom> This is found in the log: Nov 20 16:20:53 ws-thackel-01 pulseaudio[1229]: Failed to load module "module-alsa-card" (argument: "device_id="0" name="pci-0000_00_1f.3-platform-skl_hda_dsp_generic" card_name="alsa_card.pci-0000_00_1f.3-platform-skl_hda_dsp_generic" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes avoid_resampling=no | |
| [16:04] <TomTom> card_properties="module-udev-detect.discovered=1""): initialization failed. | |
| [16:57] <IrcsomeBot1> <g_padua> @Giao Linh, Guess my only option is to erase the whole SSD them | |
| [17:34] <user|2449> Hi, i need drivers for Brother printer mfc 7440n, is possible? | |
| [18:30] <Mamarok> TomTom: don't, this is a known bug, removing pipewire should do the trick | |
| [18:30] <Mamarok> unless you absolutely need it for wayland | |
| [19:02] <TomTom> Mamarok: thanks. i purged pipewire and now i have all devices in my kmixer without restarting pulseaudio. also the error message is not there. thanks! | |
| [19:06] <Sorocaba> Hi. I am trying to use zoom and they ask for password? | |
| [19:07] <Mamarok> TomTom: the bug is fairly new, I learned about it today | |
| [19:07] <Sorocaba> How can I solve it? | |
| [19:07] <Mamarok> Sorocaba: not Kubuntu related, I bet | |
| [19:08] <Sorocaba> Okay. but is there some how I can fix it? | |
| [19:08] <TomTom> Mamarok: i also searched before i asked here, but found nothing obvious (for me). again thanks. i bet i would have lived half a year with the "kill/restart" solution B-) | |
| [19:19] <Mamarok> TomTom: it surfaced in the last few weeks apparently, but the problem is identified and should get fixed with the next pipewire version | |
| === stanner is now known as hello | |
| === hello is now known as fredoman | |
| === kubuntu is now known as Guest18435 | |