Re: Pulse error using module-loopback
Aidan Gauland wrote: > On 2/09/19 6:46 am, deloptes wrote: >> Which debian and pulse audio version are you on? > > pactl info spits out this: > > Server String: /run/user/1000/pulse/native > Library Protocol Version: 32 > Server Protocol Version: 32 > Is Local: yes > Client Index: 245 > Tile Size: 65472 > User Name: aidan > Host Name: aidalbox14 > Server Name: pulseaudio > Server Version: 12.2 > Default Sample Specification: s16le 2ch 44100Hz > Default Channel Map: front-left,front-right > Default Sink: alsa_output.pci-_00_1b.0.analog-stereo > Default Source: alsa_input.usb-046d_0825_51B4D860-02.analog-mono > Cookie: 9226:7bfd > > And I'm on Debian 10.0 So what about the loopback module and the guide from the link? pactl list short sinks and use the value for the loopback. If you have trouble start the PA server with -vvv for example as described in https://fedoraproject.org/wiki/How_to_debug_PulseAudio_problems Then kill the existing server, with the command pulseaudio -k. Now launch pulseaudio -v from a console, and reproduce your problem. Provide the whole set of messages from the console where you ran pulseaudio. Also have a look here https://endless.ersoft.org/pulseaudio-loopback/
Re: How to use adminer?
Hi, > I installed adminer in debian 10 by sudo apt install adminer. > Now I am unsure how to use it on web browser. Note I installed LAMP and > already run a local setup for Wordpress. If your LAMP webroot is /var/www/html do, one way is to do the following. $ ln -s /usr/share/adminer/adminer /var/www/html and you should find adminer at http://server.example.com/adminer Alex
Re: AMD Vega 6 on Debian 10
Sven, on 2019-09-03: > On 2019-09-03 21:49 +0200, Étienne Mollier wrote: > > It is possible that your hardware is a wee bit too recent for > > Debian 10 vanilla: Vega support for the amdgpu driver landed in > > Linux 4.20, but Debian 10 ships with kernel version 4.19. > > No, the 4.20 kernel added support for the brand-new 7nm Vega20 GPUs. > Older Vega GPUs such as Alassandro's are supported in 4.19. Thank you Sven for pointing this out! You're right, I've been confused by personal experience with other chips. Installation of "firmware-amd-graphics" should be sufficient in that case. I should probably refrain to post past a certain hour in my TZ. Anyway, Kind Regards, :) -- Étienne Mollier Fingerprint: 5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d signature.asc Description: OpenPGP digital signature
How to use adminer?
I installed adminer in debian 10 by sudo apt install adminer. Now I am unsure how to use it on web browser. Note I installed LAMP and already run a local setup for Wordpress.
Re: After buster upgrade gdm login not working
By any chance, is your user account defined in a network-based authentication database, like NIS or LDAP? Yes, exactly so, it's defined by NIS. The machine where gdm login is failing is an NIS client bound to a different Debian machine (still on Debian stretch) which acts as the NIS server. On a related note, my home directory is served by NFS from the same server to this client. (I've been managing a home cluster of Linux and some other UNIXes like this for decades.) I assumed everything was working correctly with this since I can log in to the client host via ssh and at the console. --Ken
Re: After buster upgrade gdm login not working
On Wed, Sep 04, 2019 at 12:26:35PM -0400, Kenneth C. Schalk wrote: > > By any chance, is your user account defined in a network-based > > authentication database, like NIS or LDAP? > > Yes, exactly so, it's defined by NIS. https://wiki.debian.org/NewInBuster * The security settings for some components of systemd have been tightened. People using nis with systemd may encounter bug 878625 which breaks a variety of things related to login sessions. Workarounds include installing the nscd package, or reconfiguring systemd-logind.service to allow it to use the network. * If you use the nis client (ypbind), you must make sure that the YPBINDARGS= option in /etc/default/nis does not include -no-dbus. The upgrade will not modify this file, and if the -no-dbus option remains present, ypbind will fail to start, and you may not be able to login. See also: bugs 906436, 834298. * If you have user accounts in NIS, you should also double-check the /etc/nsswitch.conf file, and make sure the passwd, group and shadow lines use compat rather than files. Upgrades from systems installed as stretch should be OK, but systems originally installed as previous releases may be using deprecated configurations. I'm hearing bad things about nscd, but I have very little experience with it myself, and it's what was recommended in one of the bug reports when I was scrambling to find answers.
Re: Cannot boot after distro upgrade (SOLVED)
On 9/3/19 7:55 AM, Reco wrote: However, I wonder whether the other partitions (/, /usr, /var) shall remain ext3 in fstab, or they shall be changed to ext4 too. blkid has an answer for that. If it says that your /, /usr and /var are ext3 - leave them as that. Reco Exactly, blkid said just that. Thank you for help! I'll look for potential system misbehaviour that might be linked with the previous issue, and will report here. Misko
Re: who is verifying proposed-updates ?
PS: Sorry for sending this thrice. I did not receive a copy due to some misconfiguration. Harri
openat and graphical applications
Hello, I am just playing around with openat a little (to open a new virtual terminal and execute a command in it) and found the following problem: Though the command 'openvt -s -w -- dbus-run-session startplasmacompositor' starts KDE Plasma with Wayland, not the new terminal is used for the KDE session, but tty1, where I am currently logged in on the textual console and typed in the command. On the other hand, 'openvt -s -w -- /bin/bash" opens, as desired, a new terminal and starts the shell there. But when I enter the command 'dbus-run-session startplasmacompositor' in that shell, a switch back to tty1 takes place and the KDE session again starts there. Does anybody know the reason why not the correct TTY is used for KDE? Viele Grüße Christoph
Re: Suspicious post [was: Problème d'installation]
On Wed, Sep 04, 2019 at 10:44:23AM +0300, Reco wrote: > On Wed, Sep 04, 2019 at 09:12:54AM +0200, to...@tuxteam.de wrote: > > On Tue, Sep 03, 2019 at 11:55:02PM +0300, Reco wrote: > > [...] > > > > > This picked my interest, so I ran a decompiler on a thing. > > > Seems harmless enough - it downloads Debian libc.deb, prints OK and > > > tries to install it via dpkg. > > > > Hey, thanks :) > > > > Looks a bit... funny, still :-/ > > OP is a Canadian (timezone and language give it away) who does not > consider shell scripts "true", so they write C programs instead :) > What else could it be? Yeah, or purports to be one. And... what is this (integer?) array which is (partially) zeroed out? Looks like the random output of someone hijacking Exercise 2 to make Exercise 5 (fork & exec) or something. Cheers -- t signature.asc Description: Digital signature
Re: Suspicious post [was: Problème d'installation]
On Wed, Sep 04, 2019 at 09:12:54AM +0200, to...@tuxteam.de wrote: > On Tue, Sep 03, 2019 at 11:55:02PM +0300, Reco wrote: > [...] > > > This picked my interest, so I ran a decompiler on a thing. > > Seems harmless enough - it downloads Debian libc.deb, prints OK and > > tries to install it via dpkg. > > Hey, thanks :) > > Looks a bit... funny, still :-/ OP is a Canadian (timezone and language give it away) who does not consider shell scripts "true", so they write C programs instead :) What else could it be? Reco
Re: Suspicious post [was: Problème d'installation]
On Tue, Sep 03, 2019 at 11:55:02PM +0300, Reco wrote: > Hi. [...] > This picked my interest, so I ran a decompiler on a thing. > Seems harmless enough - it downloads Debian libc.deb, prints OK and > tries to install it via dpkg. Hey, thanks :) Looks a bit... funny, still :-/ Cheers -- t signature.asc Description: Digital signature
