SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As far as I've read from Xfce's notes at www.xfce.org , yes, they are going unmaintained because rewriting them for gstreamer-1.x was going to be too problematic, and Xfce is shifting, and has shifted from gstreamer-0.x to 1.x. You can still use xfce-volumed and xfce-mixer, but they are not officially supported any longer.
I have a machine with 64-14.1 installed that was not in use, so I decided to do a slackpkg update as my first path to beta1.
When I booted I found that I had forgotten the user and root passwords, so I booted via PXE to the -current server, mounted and chrooted to the root partition and changed passwords... then it would not boot with a lilo kernel data check error...? So again booted PXE, fsck'd no errors, mounted and chrooted and ran lilo... rebooted and logged in OK.
Not sure what that was about, surely changing passwd should not affect the boot sector or kernel, so maybe something with the mount? It is ext4, generic w/initrd.
Anyway, forgetting that, did slackpkg update to -current then manually installed the new kernel and firmware, updated lilo and reboot - all seems well on first look and listen! After some playtime with this I will likely overwrite it with a clean -current install, maybe with beta2.
So, smooth sailing as usual, so far! Thanks to all.
After running this since yesterday I can say that pulseaudio is indeed very useable, but still a little bit buggy.
When I listen to music I get the occasional crackling sound here and there. Also, when playing videos in VLC the sound sometimes starts up a second after the video started and is muted before.
Also, audio becomes more unreliable if the machine is under high load. ALSA was able to handle this just fine.
I can live with this, but it seems like there's still some crappiness involved in pulseaudio which will hopefully be fixed some time. If it gets too annoying for me, it's good to know that there's still a way to disable it.
Last edited by schmatzler; 01-14-2016 at 05:45 AM.
So output from hw:0 get recorded even though it's not supported by the chipset (with some fuzzy pulseaudio hack?)
I am afraid that I am very new to pulseaudio so at the moment I do not know why or how it works with FFmpeg and x11grab but I certainly can see it works well and easily...
After running this since yesterday I can say that pulseaudio is indeed very useable, but still a little bit buggy.
When I listen to music I get the occasional crackling sound here and there. Also, when playing videos in VLC the sound sometimes starts up a second after the video started and is muted before.
Also, audio becomes more unreliable if the machine is under high load. ALSA was able to handle this just fine.
I can live with this, but it seems like there's still some crappiness involved in pulseaudio which will hopefully be fixed some time. If it gets too annoying for me, it's good to know that there's still a way to disable it.
I can live with this, but it seems like there's still some crappiness involved in pulseaudio which will hopefully be fixed some time. If it gets too annoying for me, it's good to know that there's still a way to disable it.
As someone that has extensively used pulseaudio on multiple distros I can say gl...be glad its only that bad...
Wow... after current everything is buggy. Firefox hangs, Thunderbird hangs, cannot watch movie via SMPlayer... e.t.c. I've reinstalled NVIDIA driver. I'm not sure how to debug this? No error when launching the application via terminal, it just hangs.
People who installed my steamclient package may want to remove these three lines from the /usr/bin/steam script. If that works then I have to release an updated package:
Code:
export LD_PRELOAD='"'"'/usr/$LIB/libasound.so.2'"'"'
# Audio output goes to first "hw" device of ALSA
export SDL_AUDIODRIVER=alsa
Commenting these lines helped me to run Grim Fandango. Otherwise the game did not start (some kind of game freeze).
Guess what, I removed pulseaudio and voila, no more hangs. Seriously?
You seem to be the only person running into these issues. Could it be you grabbed your packages from a mirror that wasn't up-to-date or some packages failed to update?
It might be worth attempting to reinstall all your packages to verify they are working as they should.
You seem to be the only person running into these issues. Could it be you grabbed your packages from a mirror that wasn't up-to-date or some packages failed to update?
It might be worth attempting to reinstall all your packages to verify they are working as they should.
No, every package were installed. But ok, I will reinstall everything from another mirror. Thanks.
To be fair, it's a pretty limited sample right now.
I haven't updated my -current install yet.
That is very true, and I haven't updated my -current install in over a month (it is on my htpc, and I just needed a working APU, which -current provided... I wasn't keen on using it as a testbed). But the majority of people who've reported installing the pulseaudio update don't seem to be having the issues Bindestreck is having, which would lead most to expect it is something local. It is by no means a guarantee, but it would be the first place to start in troubleshooting.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
