Re: Getting Debian Kernel Config for 5.4 LTS Kernel

[David]

On Sun, 4 Oct 2020 at 11:34, Janis Hamme  wrote:

> I think I found a proper way to do it. It turns out the buster-backports repo
> actually has the Debian sources for all kernel versions that were released
> in the past. Maybe the steps are useful for others as well:

Hi, thank you very much for sharing your method here in detail.
I will save your guide for reference and test it out myself sometime
in future when needed.

Re: Getting Debian Kernel Config for 5.4 LTS Kernel

[Janis Hamme]

Am 04.10.20 um 00:35 schrieb deloptes:
> cp /boot/config-..xxx .config
> make .oldconfig
> make -j`nproc` bindeb-pkg
>
> as mentioned in https://wiki.debian.org/BuildADebianKernelPackage
>
> After make .oldconfig you will be asked questions about new stuff.

The oldconfig hassle is something that I'd rather like to avoid, there are a 
lot changes between 4.19 and 5.4.

I think I found a proper way to do it. It turns out the buster-backports repo 
actually has the Debian sources for all kernel versions that were released in 
the past. Maybe the steps are useful for others as well:

1. add the deb-src line for buster-backports to sources.list and update
2. "apt-cache madison linux" lists all the available source versions:

 linux | 5.4.8-1~bpo10+1 | http://ftp.de.debian.org/debian 
buster-backports/main Sources
 linux | 5.4.13-1~bpo10+1 | http://ftp.de.debian.org/debian 
buster-backports/main Sources
 linux | 5.4.19-1~bpo10+1 | http://ftp.de.debian.org/debian 
buster-backports/main Sources
 linux | 5.5.17-1~bpo10+1 | http://ftp.de.debian.org/debian 
buster-backports/main Sources
 linux | 5.6.14-2~bpo10+1 | http://ftp.de.debian.org/debian 
buster-backports/main Sources
 linux | 5.7.10-1~bpo10+1 | http://ftp.de.debian.org/debian 
buster-backports/main Sources
 linux | 5.8.10-1~bpo10+1 | http://ftp.de.debian.org/debian 
buster-backports/main Sources

3. get source with "apt-get source linux=5.4.19-1~bpo10+1"
4. cd to source and run

make -f debian/rules.gen setup_amd64

This will just generate the .config for the Debian 5.4.19 amd64 kernel at 
debian/build/build_amd64_none_amd64/.config

5. copy config to vanilla 5.4.69 kernel tree, run make oldconfig (almost 
nothing to do)

6. disable signing options

scripts/config --disable MODULE_SIG
scripts/config --disable SYSTEM_TRUSTED_KEYRING

7. build kernel as usual with "make deb-pkg" and be happy

Regards
Janis

Re: How to disable the screen locker on amd64 buster?

[Gene Heskett]

On Saturday 03 October 2020 11:21:04 Dan Ritter wrote:

> Gene Heskett wrote:
> > On Saturday 03 October 2020 08:12:56 Dan Ritter wrote:
> > > I would try
> > >
> > > apt remove lightdm light-locker
> >
> > and task-xfce, the meta installer file was also selected
> >
> > > and either installing xdm or just using startx to get X11 and
> > > XFCE up when you want it.
> >
> > Which is for me, 100% of the time, so xdm installed.
> >
> > > -dsr
> >
> > did that and installed xdm, reboot is next. But apt claimed there
> > were several hundred packages (353 count) that could be autoremoved.
> >  Is that normal after an iso install and update to 10.6? I did the
> > autoremove, linuxcnc still runs, so I think we are in business. 34
> > minutes after the reboot:
>
> Lots of autoremovable packages are normal. I generally keep them
> unless I have a space crunch.

I've no crunch, its a 2T drive, but killed them anyway
> > Screen Saver:
> >   prefer blanking:  noallow exposures:  yes
> >   timeout:  0cycle:  0
> > DPMS (Energy Star):
> >   Standby: 450Suspend: 600Off: 900
> >   DPMS is Disabled
> >
> > I believe thats what we wanted.
>
> Exactly so.
>
On inspection from its own screen, I have an odd problem.
The login I am seeing now has a huge debian logo, so I assume (there's that 
word again, thats from xdm.

I can type and see my username in the usename box, and pressing enter then 
outlnes the passwd box.  But after that, the keyboard is not showing anything 
in the passwd box.  And of course I cannot login from its own keyboard.

So how can I restore that to normal function?

Thanks.

> > The above now shows blanking off, expose on, and DPMS off after the
> > reboot and no one has yet logged in locally, looks good.
> >
> > Thanks a bunch, Dan
>
> Not a problem. Thanks for stating your issue clearly.
>
> -dsr-


Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: Getting Debian Kernel Config for 5.4 LTS Kernel

[deloptes]

Janis Hamme wrote:

> I'd like to build the vanilla 5.4.69 LTS Kernel for one of my Debian
> machines (Buster).
> 
> The easiest way seems to build the Kernel with the built in "make
> deb-pkg" target. Since I do not really want to go through all the config
> changes,
> my plan was to get a 5.4 config for amd64 from
> https://salsa.debian.org/kernel-team/linux
> 
> I cloned the git repository and checked out the 5.4.19-1_bpo10+1 tag.
> But the config seems do be manged somehow by the Debian build system and
> is split across multiple files for different architectures and feature
> sets etc. Does someone know how I can generate the final amd64 config to
> use it for my custom kernel?
> 

cp /boot/config-..xxx .config
make .oldconfig
make -j`nproc` bindeb-pkg

as mentioned in https://wiki.debian.org/BuildADebianKernelPackage

After make .oldconfig you will be asked questions about new stuff.

> Updating the Debian package sources for 5.4.69 would also work. It
> probably easy, but I didn't find any documentation or tutorials on it (I
> also don't really want to deal with the Debian custom patches that
> probably won't apply properly to Vanilla 5.4.69)

Actually it is not a bad idea to use the debian kernel with the patches,
especially if you are on public network.

Getting Debian Kernel Config for 5.4 LTS Kernel

[Janis Hamme]

Hi,

I'd like to build the vanilla 5.4.69 LTS Kernel for one of my Debian
machines (Buster).

The easiest way seems to build the Kernel with the built in "make
deb-pkg" target. Since I do not really want to go through all the config
changes,
my plan was to get a 5.4 config for amd64 from
https://salsa.debian.org/kernel-team/linux

I cloned the git repository and checked out the 5.4.19-1_bpo10+1 tag.
But the config seems do be manged somehow by the Debian build system and
is split across multiple files for different architectures and feature
sets etc. Does someone know how I can generate the final amd64 config to
use it for my custom kernel?

Updating the Debian package sources for 5.4.69 would also work. It
probably easy, but I didn't find any documentation or tutorials on it (I
also don't really want to deal with the Debian custom patches that
probably won't apply properly to Vanilla 5.4.69)

Regards
Janis

Re: Missing i915 activity at boot time

[Felix Miata]

Rafa composed on 2020-10-03 17:44 (UTC+0200):

> I have recently got a laptop with Intel UHD620 integrated graphics.


looks likely relevant to your needs.
-- 
Evolution as taught in public schools, like religion,
is based on faith, not on science.

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: can't boot to a graphical interface.

[Patrick Bartek]

On Sat, 3 Oct 2020 13:39:22 -0400
Frank McCormick  wrote:

> On 10/3/20 11:20 AM, Kent West wrote:
> > 
> > 
> > On Sat, Oct 3, 2020 at 8:01 AM songbird  > > wrote:
> > 
> > Frank McCormick wrote:  
> >  > While compiling an application today my Debian bullseye
> >  > system  
> > somehow  
> >  > got messed up. It will boot to a CLI but no X, apparently
> >  > because  
> > for  
> >  > some reason the system is unable to access some files in
> >  > /usr/share/dbus-1. It keeps saying access denied. The
> >  > directories  
> > and  
> >  > files are owned by root, and if I noot to a CLI I have no
> >  > trouble accessing them using sudo and midnight commander.
> >  >
> >  > I tried reinstalling systemd but it ended with the same
> >  > problem.  
> > 
> > 
> > On my bullseye/sid lappie, for comparison to yours:
> > 
> > kent@westk-9463:~$ ls -lah /usr/share/dbus-1/
> > total 84K
> > drwxr-xr-x   8 root root 4.0K Sep 17 19:55 .
> > drwxr-xr-x 610 root root  20K Sep  5 16:26 ..
> > drwxr-xr-x   2 root root 4.0K Aug  6 20:50 accessibility-services
> > drwxr-xr-x   2 root root  12K Aug  6 21:03 interfaces
> > drwxr-xr-x   2 root root  20K Aug  6 20:55 services
> > -rw-r--r--   1 root root 3.6K Jul  2 08:19 session.conf
> > drwxr-xr-x   2 root root 4.0K Sep 17 19:55 session.d
> > -rw-r--r--   1 root root 5.7K Jul  2 08:19 system.conf
> > drwxr-xr-x   2 root root 4.0K Sep 17 19:55 system.d
> > drwxr-xr-x   2 root root 4.0K Aug  6 21:08 system-services
> > 
> > kent@westk-9463:~$ ls -lahd /usr/share/dbus-1/
> > drwxr-xr-x 8 root root 4.0K Sep 17 19:55 /usr/share/dbus-1/
> >   
> 
> 
> My system now is back to **normal**. I re-installed
> about a dozen packages including systemd.
> I also changed one mode  to match yours.
> 
> frank@franklin:~$ ls -lah /usr/share/dbus-1/
> total 44K
> drwxr-xr-x   6 root root 4.0K Oct  3 10:08 .
> drwxr-xr-x 246 root root  12K Oct  2 16:56 ..
> drwxr-xr-x   2 root root 4.0K Oct  3 10:08 interfaces
> drwxr-xr-x   2 root root 4.0K Oct  3 09:20 services
> -rw-r--r--   1 root root 3.6K Jul  2 09:19 session.conf
> -rw-r--r--   1 root root 5.7K Jul  2 09:19 system.conf
> drwxr-xr-x   2 root root 4.0K Oct  3 10:08 system.d
> drwxr-xr-x   2 root root 4.0K Oct  3 10:08 system-services
> 
> Still don't know what the h*ll happened.

You are using "testing" and an Alpha 2 Release after all.  So, expect
the occassional "gotcha."  It's the nature of the beast.

B

Re: GUI programma met root-rechten, w.s. policykit

[Paul van der Vlis]

Op 03-10-2020 om 21:27 schreef Paul van der Vlis:

> Bij de computer waar het goed gaat, heb ik nooit iets gewijzigd aan de
> configuratie van policykit voor zover ik weet. Hooguit voor wat betreft
> het recht van gewone users om af te kunnen sluiten of te rebooten.
> Hier gebruik ik Cinnamon als desktop.
> 
> De computer waar het niet goed gaat is vers geinstalleerd en heeft XFCE
> als desktop.

De computer waar alles goed gaat heeft ook een XFCE desktop. Die heb ik
ook even geprobeerd en daar gaat alles ook goed. Het lijkt dus niets met
de desktop te maken te hebben.

Groet,
Paul


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: GUI programma met root-rechten, w.s. policykit

[Paul van der Vlis]

Op 03-10-2020 om 20:59 schreef Geert Stappers:
> On Sat, Oct 03, 2020 at 08:04:22PM +0200, Paul van der Vlis wrote:
>> Op 03-10-2020 om 19:22 schreef Geert Stappers:
>>> On Sat, Oct 03, 2020 at 06:56:41PM +0200, Paul van der Vlis wrote:
 Hoi,

 Sommige GUI programma's hebben (soms) root rechten nodig, denk
 bijvoorbeeld aan het programma "gnome-software", wat dient om
 programma's te installeren. Mooi programma overigens.

 Het krijgen van die root-rechten werkt tegenwoordig met "policykit",
 daar heb ik weinig verstand van.

 Nu heb ik machines waar het netjes werkt. Op het moment dat
 Gnome-software root rechten nodig heeft vraagt het om het paswoord van
 root. Op een andere machine gaat het niet goed, daar wordt niet gevraagd
 om dat paswoord en dan heeft het programma niet genoeg rechten.

 Hoe zorg ik ervoor dat dit venster wat om een paswoord vraagt verschijnt?
>>>
>>> Beide computers zou ik `id  account` doen. "account" is de accountnaam 
>>> van de user die de grafische login deed.
>>>
>>> Vervolgens verschillen zoeken.
>>>
>>> Mijn inschatting is dat op de werkende computer account wel in de groep
>>> sudo of zo zit.
>>
>> Nee, de user op de computer waar het werkt is "gast", en die heeft juist
>> bijzonder weinig rechten.
> 
> "weinig rechten" ?Misschien:  "weinig groepen"  ??
> 
>  
>> De user op de computer waar het niet werkt heeft alle rechten van de
>> user gast, maar zit nog in een paar groepen meer die volgens mij niet
>> van belang zijn hier ("floppy", "cdrom", "lpadmin", "dip").
>>
>> Maar dit gaat ook niet via sudo, maar via policykit...
> 
> En weten we waar policykit zijn beleid op baseerd?
> 
> Ik bedoel: Ergens zal toch moeten staan wie wat mag.
> 
> (Ja, dat is misschien waar deze thread over gaat.)

Ik wou eigenlijk niet een bepaalde user meer rechten geven. Maar dat er
om het root-paswoord wordt gevraagd als die rechten nodig zijn.

Interessant is wellicht nog om te melden dat het programma
gnome-software start als gewone gebruiker. Pas op het moment dat je iets
wilt installeren of verwijderen wordt er gevraagd om het root-paswoord.

Bij de computer waar het goed gaat, heb ik nooit iets gewijzigd aan de
configuratie van policykit voor zover ik weet. Hooguit voor wat betreft
het recht van gewone users om af te kunnen sluiten of te rebooten.
Hier gebruik ik Cinnamon als desktop.

De computer waar het niet goed gaat is vers geinstalleerd en heeft XFCE
als desktop.

Groet,
Paul





-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: LaTeX et LaTeXila

[sub0]

Le 02/10/2020 à 17:08:28 (+0200), f6k a écrit :
> Bonjour,
> 
> On Thu, Oct 01, 2020 at 07:54:57PM +0200, F. Dubois wrote:
> 
> > Voici la commande qui pose souci :
> > 
> > \newcommand{\encadrecouleur}[2]{\psframebox[fillstyle=solid,fillcolor=#1,framearc=0.15]{\begin{minipage}{\columnwidth-25\fboxsep}#2\end{minipage}}}
> 
> Je vois que les réponses ne se bousculent pas (encore !), donc je me
> permets.  Pour de l'aide autour de LaTeX, je te conseille vivement
> d'aller faire un tour sur le groupe de nouvelle fr.comp.text.tex.  Il
> est nécessaire effectivement d'avoir un accès quelconque à usenet, mais
> c'est là que je trouve les meilleures discussions et l'aide la plus
> substantielle autour de LaTeX.  En espérant que, si tu n'obtiens pas
> l'aide souhaitée par ici, tu puisses trouver ton chemin vers ce groupe.
> 
> -f6k

Il y a également https://texnique.fr/ qui mérite d’être dans les marque-pages.

Re: GUI programma met root-rechten, w.s. policykit

[Geert Stappers]

On Sat, Oct 03, 2020 at 08:04:22PM +0200, Paul van der Vlis wrote:
> Op 03-10-2020 om 19:22 schreef Geert Stappers:
> > On Sat, Oct 03, 2020 at 06:56:41PM +0200, Paul van der Vlis wrote:
> >> Hoi,
> >>
> >> Sommige GUI programma's hebben (soms) root rechten nodig, denk
> >> bijvoorbeeld aan het programma "gnome-software", wat dient om
> >> programma's te installeren. Mooi programma overigens.
> >>
> >> Het krijgen van die root-rechten werkt tegenwoordig met "policykit",
> >> daar heb ik weinig verstand van.
> >>
> >> Nu heb ik machines waar het netjes werkt. Op het moment dat
> >> Gnome-software root rechten nodig heeft vraagt het om het paswoord van
> >> root. Op een andere machine gaat het niet goed, daar wordt niet gevraagd
> >> om dat paswoord en dan heeft het programma niet genoeg rechten.
> >>
> >> Hoe zorg ik ervoor dat dit venster wat om een paswoord vraagt verschijnt?
> > 
> > Beide computers zou ik `id  account` doen. "account" is de accountnaam 
> > van de user die de grafische login deed.
> > 
> > Vervolgens verschillen zoeken.
> > 
> > Mijn inschatting is dat op de werkende computer account wel in de groep
> > sudo of zo zit.
> 
> Nee, de user op de computer waar het werkt is "gast", en die heeft juist
> bijzonder weinig rechten.

"weinig rechten" ?Misschien:  "weinig groepen"  ??

 
> De user op de computer waar het niet werkt heeft alle rechten van de
> user gast, maar zit nog in een paar groepen meer die volgens mij niet
> van belang zijn hier ("floppy", "cdrom", "lpadmin", "dip").
> 
> Maar dit gaat ook niet via sudo, maar via policykit...

En weten we waar policykit zijn beleid op baseerd?

Ik bedoel: Ergens zal toch moeten staan wie wat mag.

(Ja, dat is misschien waar deze thread over gaat.)




Regards
Geert Stappers
-- 
Silence is hard to parse

Re: Missing i915 activity at boot time

[Rafa]

Hi,

On Sat, Oct 03, 2020 at 06:36:42PM +0200, Hans wrote:

> Am Samstag, 3. Oktober 2020, 17:44:30 CEST schrieb Rafa:
> Hi,
> 
> did you install the packages firmware-linux-free and firmware-linux-nonfree?

I had installed firmware-linux-free but not firmware-linux-nonfree.

I have installed it right now and have checked again, but nothing seems to have
changed.

(I also have intel-microcode installed.)

> Also check, if the firmware exists in /lib/firmware/i915

It seems so:

  $ ls -1 /lib/firmware/i915/
  bxt_dmc_ver1_07.bin
  bxt_dmc_ver1.bin
  bxt_guc_ver8_7.bin
  bxt_guc_ver9_29.bin
  bxt_huc_ver01_07_1398.bin
  cnl_dmc_ver1_07.bin
  glk_dmc_ver1_04.bin
  kbl_dmc_ver1_01.bin
  kbl_dmc_ver1_04.bin
  kbl_dmc_ver1.bin
  kbl_guc_ver9_14.bin
  kbl_guc_ver9_39.bin
  kbl_huc_ver02_00_1810.bin
  skl_dmc_ver1_23.bin
  skl_dmc_ver1_26.bin
  skl_dmc_ver1_27.bin
  skl_dmc_ver1.bin
  skl_guc_ver1.bin
  skl_guc_ver4.bin
  skl_guc_ver6_1.bin
  skl_guc_ver6.bin
  skl_guc_ver9_33.bin
  skl_huc_ver01_07_1398.bin

> 
> Good luck!

Thaks.

> Hans
> 
> [...]

Regards,

Rafa.


signature.asc
Description: PGP signature

Re: GUI programma met root-rechten

[Paul van der Vlis]

Op 03-10-2020 om 19:22 schreef Geert Stappers:
> On Sat, Oct 03, 2020 at 06:56:41PM +0200, Paul van der Vlis wrote:
>> Hoi,
>>
>> Sommige GUI programma's hebben (soms) root rechten nodig, denk
>> bijvoorbeeld aan het programma "gnome-software", wat dient om
>> programma's te installeren. Mooi programma overigens.
>>
>> Het krijgen van die root-rechten werkt tegenwoordig met "policykit",
>> daar heb ik weinig verstand van.
>>
>> Nu heb ik machines waar het netjes werkt. Op het moment dat
>> Gnome-software root rechten nodig heeft vraagt het om het paswoord van
>> root. Op een andere machine gaat het niet goed, daar wordt niet gevraagd
>> om dat paswoord en dan heeft het programma niet genoeg rechten.
>>
>> Hoe zorg ik ervoor dat dit venster wat om een paswoord vraagt verschijnt?
> 
> Beide computers zou ik `id  account` doen. "account" is de accountnaam 
> van de user die de grafische login deed.
> 
> Vervolgens verschillen zoeken.
> 
> Mijn inschatting is dat op de werkende computer account wel in de groep
> sudo of zo zit.

Nee, de user op de computer waar het werkt is "gast", en die heeft juist
bijzonder weinig rechten.

De user op de computer waar het niet werkt heeft alle rechten van de
user gast, maar zit nog in een paar groepen meer die volgens mij niet
van belang zijn hier ("floppy", "cdrom", "lpadmin", "dip").

Maar dit gaat ook niet via sudo, maar via policykit...

Groet,
Paul


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

Re: GUI programma met root-rechten

[Paul van der Vlis]

Op 03-10-2020 om 19:20 schreef Vincent Lammens:
> On 10/3/20 6:56 PM, Paul van der Vlis wrote:
>> Hoi,
>>
>> Sommige GUI programma's hebben (soms) root rechten nodig, denk
>> bijvoorbeeld aan het programma "gnome-software", wat dient om
>> programma's te installeren. Mooi programma overigens.
>>
>> Het krijgen van die root-rechten werkt tegenwoordig met "policykit",
>> daar heb ik weinig verstand van.
>>
>> Nu heb ik machines waar het netjes werkt. Op het moment dat
>> Gnome-software root rechten nodig heeft vraagt het om het paswoord van
>> root. Op een andere machine gaat het niet goed, daar wordt niet gevraagd
>> om dat paswoord en dan heeft het programma niet genoeg rechten.
>>
>> Hoe zorg ik ervoor dat dit venster wat om een paswoord vraagt verschijnt?
>>
>> Groet,
>> Paul
>>
>>
> Hey
> 
> Ik weet dat in Debian stretch er "gksu" was, waarmee je een
> gui-programma als root kon uitvoeren.
> 
> https://manpages.debian.org/stretch/gksu/gksudo.1.en.html

Inderdaad, maar dat is niet meer.

> Voor buster je wel gebruik maken van "pkexec"
> 
> https://manpages.debian.org/buster/policykit-1/pkexec.1.en.html
> 
> Misschien kan het programma zo uitvoeren helpen?

Ik ben eigenlijk niet op zoek naar een noodoplossing, maar naar de echte
oplosssing. Op de andere computer gaat het immers ook netjes.

Uiteraard heb ik policykit-1 geinstalleerd, dus ik heb het bestand
/usr/bin/pkexec .

Groet,
Paul


-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/



signature.asc
Description: OpenPGP digital signature

Re: can't boot to a graphical interface.

[Frank McCormick]

On 10/3/20 11:20 AM, Kent West wrote:



On Sat, Oct 3, 2020 at 8:01 AM songbird > wrote:


Frank McCormick wrote:
 > While compiling an application today my Debian bullseye system
somehow
 > got messed up. It will boot to a CLI but no X, apparently because
for
 > some reason the system is unable to access some files in
 > /usr/share/dbus-1. It keeps saying access denied. The directories
and
 > files are owned by root, and if I noot to a CLI I have no trouble
 > accessing them using sudo and midnight commander.
 >
 > I tried reinstalling systemd but it ended with the same problem.


On my bullseye/sid lappie, for comparison to yours:

kent@westk-9463:~$ ls -lah /usr/share/dbus-1/
total 84K
drwxr-xr-x   8 root root 4.0K Sep 17 19:55 .
drwxr-xr-x 610 root root  20K Sep  5 16:26 ..
drwxr-xr-x   2 root root 4.0K Aug  6 20:50 accessibility-services
drwxr-xr-x   2 root root  12K Aug  6 21:03 interfaces
drwxr-xr-x   2 root root  20K Aug  6 20:55 services
-rw-r--r--   1 root root 3.6K Jul  2 08:19 session.conf
drwxr-xr-x   2 root root 4.0K Sep 17 19:55 session.d
-rw-r--r--   1 root root 5.7K Jul  2 08:19 system.conf
drwxr-xr-x   2 root root 4.0K Sep 17 19:55 system.d
drwxr-xr-x   2 root root 4.0K Aug  6 21:08 system-services

kent@westk-9463:~$ ls -lahd /usr/share/dbus-1/
drwxr-xr-x 8 root root 4.0K Sep 17 19:55 /usr/share/dbus-1/




My system now is back to **normal**. I re-installed
about a dozen packages including systemd.
I also changed one mode  to match yours.

frank@franklin:~$ ls -lah /usr/share/dbus-1/
total 44K
drwxr-xr-x   6 root root 4.0K Oct  3 10:08 .
drwxr-xr-x 246 root root  12K Oct  2 16:56 ..
drwxr-xr-x   2 root root 4.0K Oct  3 10:08 interfaces
drwxr-xr-x   2 root root 4.0K Oct  3 09:20 services
-rw-r--r--   1 root root 3.6K Jul  2 09:19 session.conf
-rw-r--r--   1 root root 5.7K Jul  2 09:19 system.conf
drwxr-xr-x   2 root root 4.0K Oct  3 10:08 system.d
drwxr-xr-x   2 root root 4.0K Oct  3 10:08 system-services

Still don't know what the h*ll happened.

Thanks Kent
--
Frank McCormick

Re: GUI programma met root-rechten

[Vincent Lammens]

On 10/3/20 6:56 PM, Paul van der Vlis wrote:
> Hoi,
> 
> Sommige GUI programma's hebben (soms) root rechten nodig, denk
> bijvoorbeeld aan het programma "gnome-software", wat dient om
> programma's te installeren. Mooi programma overigens.
> 
> Het krijgen van die root-rechten werkt tegenwoordig met "policykit",
> daar heb ik weinig verstand van.
> 
> Nu heb ik machines waar het netjes werkt. Op het moment dat
> Gnome-software root rechten nodig heeft vraagt het om het paswoord van
> root. Op een andere machine gaat het niet goed, daar wordt niet gevraagd
> om dat paswoord en dan heeft het programma niet genoeg rechten.
> 
> Hoe zorg ik ervoor dat dit venster wat om een paswoord vraagt verschijnt?
> 
> Groet,
> Paul
> 
> 
Hey

Ik weet dat in Debian stretch er "gksu" was, waarmee je een
gui-programma als root kon uitvoeren.

https://manpages.debian.org/stretch/gksu/gksudo.1.en.html

Voor buster je wel gebruik maken van "pkexec"

https://manpages.debian.org/buster/policykit-1/pkexec.1.en.html

Misschien kan het programma zo uitvoeren helpen?

-- 
Met vriendelijke groeten

Vincent Lammens
https://www.vincentlammens.be


0x2EDA63E1FE5E3763.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: Missing i915 activity at boot time

[Hans]

Am Samstag, 3. Oktober 2020, 17:44:30 CEST schrieb Rafa:
Hi,

did you install the packages firmware-linux-free and firmware-linux-nonfree?

Also check, if the firmware exists in /lib/firmware/i915

Good luck!

Hans

> Hi,
> 
> I have recently got a laptop with Intel UHD620 integrated graphics.
> 
> The laptop was shipped with Debian 10.4 installed.
> 
> The output of dmesg, as shipped, contained these messages regarding i915:
> 
> # dmesg | grep -i i915
> [2.215117] i915 :00:02.0: [drm] VT-d active for gfx access
> [2.215212] i915 :00:02.0: vgaarb: deactivate vga console
> [2.216629] i915 :00:02.0: vgaarb: changed VGA decodes:
> olddecodes=io+mem,decodes=io+mem:owns=io+mem [2.216651] i915
> :00:02.0: firmware: failed to load i915/kbl_dmc_ver1_04.bin (-2) [   
> 2.216655] i915 :00:02.0: Direct firmware load for
> i915/kbl_dmc_ver1_04.bin failed with error -2 [2.216656] i915
> :00:02.0: [drm] Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin.
> Disabling runtime power management. [2.216656] i915 :00:02.0: [drm]
> DMC firmware homepage:
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
> /tree/i915 [3.394853] [drm] Initialized i915 1.6.0 20200515 for
> :00:02.0 on minor 0 [3.416309] fbcon: i915drmfb (fb0) is primary
> device
> [3.443643] i915 :00:02.0: fb0: i915drmfb frame buffer device
> [4.263369] snd_hda_intel :00:1f.3: bound :00:02.0 (ops
> i915_audio_component_bind_ops [i915])
> 
> 
> Now, I am in the process of installing Debian 10.6 in the same laptop (a new
> install, not upgrade). But cannot get the graphical environment up and
> running.
> 
> The only message related to i915 reported by dmesg currently is:
> 
> # dmesg | grep -i i915
> [4.709347] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel
> HDMI/DP codec
> 
> Unfortunately, I do not have enough background to understand why I am not
> getting similar messages than the ones I got previously, but I guess this
> lack of "i915 activity" at boot time could be related to the problems I am
> facing to start Xorg.
> 
> Any hints would be appreciated.
> 
> Thanks.
> 
> Rafa.



signature.asc
Description: This is a digitally signed message part.

Re: LaTeX et LaTeXila

[F. Dubois]

Le 02/10/2020 à 17:08, f6k a écrit :

Bonjour,

On Thu, Oct 01, 2020 at 07:54:57PM +0200, F. Dubois wrote:


Voici la commande qui pose souci :

\newcommand{\encadrecouleur}[2]{\psframebox[fillstyle=solid,fillcolor=#1,framearc=0.15]{\begin{minipage}{\columnwidth-25\fboxsep}#2\end{minipage}}}

Je vois que les réponses ne se bousculent pas (encore !), donc je me
permets.  Pour de l'aide autour de LaTeX, je te conseille vivement
d'aller faire un tour sur le groupe de nouvelle fr.comp.text.tex.  Il
est nécessaire effectivement d'avoir un accès quelconque à usenet, mais
c'est là que je trouve les meilleures discussions et l'aide la plus
substantielle autour de LaTeX.  En espérant que, si tu n'obtiens pas
l'aide souhaitée par ici, tu puisses trouver ton chemin vers ce groupe.

-f6k

Merci de la réponse. Bon pour LaTeX je me doutais qu'il faut mieux aller 
voir un groupe dédié.
Par contre LaTeXila doit avoir un petit souci, et ça c'est plutôt bien 
du domaine de debian.

Fabien

Missing i915 activity at boot time

[Rafa]

Hi,

I have recently got a laptop with Intel UHD620 integrated graphics.

The laptop was shipped with Debian 10.4 installed.

The output of dmesg, as shipped, contained these messages regarding i915:

# dmesg | grep -i i915
[2.215117] i915 :00:02.0: [drm] VT-d active for gfx access
[2.215212] i915 :00:02.0: vgaarb: deactivate vga console
[2.216629] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
[2.216651] i915 :00:02.0: firmware: failed to load 
i915/kbl_dmc_ver1_04.bin (-2)
[2.216655] i915 :00:02.0: Direct firmware load for 
i915/kbl_dmc_ver1_04.bin failed with error -2
[2.216656] i915 :00:02.0: [drm] Failed to load DMC firmware 
i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.
[2.216656] i915 :00:02.0: [drm] DMC firmware homepage: 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[3.394853] [drm] Initialized i915 1.6.0 20200515 for :00:02.0 on minor 0
[3.416309] fbcon: i915drmfb (fb0) is primary device
[3.443643] i915 :00:02.0: fb0: i915drmfb frame buffer device
[4.263369] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])


Now, I am in the process of installing Debian 10.6 in the same laptop (a new 
install, not upgrade). But cannot get the graphical environment up and running.

The only message related to i915 reported by dmesg currently is:

# dmesg | grep -i i915
[4.709347] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel 
HDMI/DP codec

Unfortunately, I do not have enough background to understand why I am not 
getting similar messages than the ones I got previously, but I guess this lack 
of "i915 activity" at boot time could be related to the problems I am facing to 
start Xorg.

Any hints would be appreciated.

Thanks.

Rafa.


signature.asc
Description: PGP signature

Re: How to disable the screen locker on amd64 buster?

[Gene Heskett]

On Saturday 03 October 2020 11:21:04 Dan Ritter wrote:

> Gene Heskett wrote:
> > On Saturday 03 October 2020 08:12:56 Dan Ritter wrote:
> > > I would try
> > >
> > > apt remove lightdm light-locker
> >
> > and task-xfce, the meta installer file was also selected
> >
> > > and either installing xdm or just using startx to get X11 and
> > > XFCE up when you want it.
> >
> > Which is for me, 100% of the time, so xdm installed.
> >
> > > -dsr
> >
> > did that and installed xdm, reboot is next. But apt claimed there
> > were several hundred packages (353 count) that could be autoremoved.
> >  Is that normal after an iso install and update to 10.6? I did the
> > autoremove, linuxcnc still runs, so I think we are in business. 34
> > minutes after the reboot:
>
> Lots of autoremovable packages are normal. I generally keep them
> unless I have a space crunch.
>
> > Screen Saver:
> >   prefer blanking:  noallow exposures:  yes
> >   timeout:  0cycle:  0
> > DPMS (Energy Star):
> >   Standby: 450Suspend: 600Off: 900
> >   DPMS is Disabled
> >
> > I believe thats what we wanted.
>
> Exactly so.
>
> > The above now shows blanking off, expose on, and DPMS off after the
> > reboot and no one has yet logged in locally, looks good.
> >
> > Thanks a bunch, Dan
>
> Not a problem. Thanks for stating your issue clearly.
>
> -dsr-
And to you, Dan, you knew exactly what I wanted.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: How to disable the screen locker on amd64 buster?

[Gene Heskett]

On Saturday 03 October 2020 08:56:33 Andrew M.A. Cater wrote:

> On Sat, Oct 03, 2020 at 04:27:08AM -0400, Gene Heskett wrote:
> > The computer is controlling high powered machinery. Having the
> > screen locker kick in, disabling our access to the application until
> > we have wasted a minute typing on a poor keyboard trying to log back
> > in can be quite dangerous when the machine has a runaway. Anything
> > we do with xset is overridden before the 10 minute timeout is done.
>
> Gene,
>
> You've been asking similar questions for years on various of the
> Debian lists - - real time kernel, how to do things on Raspberry Pi,
> generically on ARM ...
>
> Yours is a niche case: not many of us have lathes hooked up to Linux
> boxes.

I think you miss-count us, Andrew. There are, I would estimate well over 
1000 world wide users of LinuxCNC, but most are more mechanics than code 
carvers.  They rarely show up on a mailing list, bugging the vendor that 
sold them the package, having bought a software package for a sizeable 
yearly seat fee because it makes them money in their shops. But while 
they may make heavy use of those code generators, they are feeding that 
output into linuxcnc about 25% of the time.  There are of course 
commercial machine control packages, but they can run into the 5th 
digit, and most are frozen in the 1970's for features we've been doing 
better for many years. They are stuck at 4 axises, we've been doing 9 
for decades. At one time it was ITAR software, because it could carve a 
submarine screw that didn't cavitate but Hitachi-America shipped it on a 
machine that found its way to china, and now the whole world knows how 
to machine quiet screws for their submarines.  Horse out of the barn, 
hitachi got a wrist slap, and we were taken off the ITAR list.

> Have you considered not using a desktop environment at all rather than
> trying to expect the rest of us to run through problems we don't
> understand? We're not being collectively unintelligent but this would
> be easier if we could all get to one topic at a time :)

> > Some of us like xfce4, please advise how to permanently disable
> > lightdm and its light-locker. _Forever_. We do know how to turn off
> > the monitor at the end of the day.
>
> As suggested elsewhere : remove lightdm. Maybe work out just which
> programs you _must_ run and strip down a desktop environment / an X
> environment to just run that stuff. That might  take time - and you
> might not be able to get down to nothing extraneous but it would be a
> start. Pencil, paper and a plan splitting things down to single steps
> or areas of concern might help significantly here and elsewhere.

But that also limits what the machine can otherwise do. I have cat6 to 
every machine and every machine can look up what I need to know on the 
net. I wouldn't have it any other way, but then I am also a hobbyist in 
my dotage.  Retired from a tv Chief Engineer's chair I warmed for 18 
years, and workbench as a CET, but still keeping the local radio station 
on the air.

> All the best
>
> Andy C.

Than you Andy C, and have a virtual near beer with me tomorrow as I 
celebrate the 86th. Diabetics aren't supposed to drink the real stuff.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: can't boot to a graphical interface.

[Kent West]

On Sat, Oct 3, 2020 at 8:01 AM songbird  wrote:

> Frank McCormick wrote:
> > While compiling an application today my Debian bullseye system somehow
> > got messed up. It will boot to a CLI but no X, apparently because for
> > some reason the system is unable to access some files in
> > /usr/share/dbus-1. It keeps saying access denied. The directories and
> > files are owned by root, and if I noot to a CLI I have no trouble
> > accessing them using sudo and midnight commander.
> >
> > I tried reinstalling systemd but it ended with the same problem.
>
>
On my bullseye/sid lappie, for comparison to yours:

kent@westk-9463:~$ ls -lah /usr/share/dbus-1/
total 84K
drwxr-xr-x   8 root root 4.0K Sep 17 19:55 .
drwxr-xr-x 610 root root  20K Sep  5 16:26 ..
drwxr-xr-x   2 root root 4.0K Aug  6 20:50 accessibility-services
drwxr-xr-x   2 root root  12K Aug  6 21:03 interfaces
drwxr-xr-x   2 root root  20K Aug  6 20:55 services
-rw-r--r--   1 root root 3.6K Jul  2 08:19 session.conf
drwxr-xr-x   2 root root 4.0K Sep 17 19:55 session.d
-rw-r--r--   1 root root 5.7K Jul  2 08:19 system.conf
drwxr-xr-x   2 root root 4.0K Sep 17 19:55 system.d
drwxr-xr-x   2 root root 4.0K Aug  6 21:08 system-services

kent@westk-9463:~$ ls -lahd /usr/share/dbus-1/
drwxr-xr-x 8 root root 4.0K Sep 17 19:55 /usr/share/dbus-1/

Re: How to disable the screen locker on amd64 buster?

[Dan Ritter]

Gene Heskett wrote: 
> On Saturday 03 October 2020 08:12:56 Dan Ritter wrote:
> >
> > I would try
> >
> > apt remove lightdm light-locker
> and task-xfce, the meta installer file was also selected
> > and either installing xdm or just using startx to get X11 and
> > XFCE up when you want it.
> 
> Which is for me, 100% of the time, so xdm installed.
> 
> > -dsr
> 
> did that and installed xdm, reboot is next. But apt claimed there were 
> several hundred packages (353 count) that could be autoremoved.  Is that 
> normal after an iso install and update to 10.6? I did the autoremove, 
> linuxcnc still runs, so I think we are in business. 34 minutes after the 
> reboot:

Lots of autoremovable packages are normal. I generally keep them
unless I have a space crunch.

> Screen Saver:
>   prefer blanking:  noallow exposures:  yes
>   timeout:  0cycle:  0
> DPMS (Energy Star):
>   Standby: 450Suspend: 600Off: 900
>   DPMS is Disabled
> 
> I believe thats what we wanted.

Exactly so.

> The above now shows blanking off, expose on, and DPMS off after the 
> reboot and no one has yet logged in locally, looks good.
> 
> Thanks a bunch, Dan

Not a problem. Thanks for stating your issue clearly.

-dsr-

Re: How to disable the screen locker on amd64 buster?

[David Wright]

On Sat 03 Oct 2020 at 04:27:08 (-0400), Gene Heskett wrote:
> The computer is controlling high powered machinery. Having the screen 
> locker kick in, disabling our access to the application until we have 
> wasted a minute typing on a poor keyboard trying to log back in can be 
> quite dangerous when the machine has a runaway. Anything we do with xset 
> is overridden before the 10 minute timeout is done.

Sounds like time for a visit from OSHA, HSE, or whoever.

> Some of us like xfce4, please advise how to permanently disable lightdm 
> and its light-locker. _Forever_. We do know how to turn off the monitor 
> at the end of the day.

Use a window manager, so you can select the software present
and constrain the display's behaviour.

Cheers,
David.

Bug Report

[thinkingtwice]

Hello,

Having gone through Debian's ReportBug system, I am unsure which packages the 
issue is coming from hence the email contact.

The problem is quite straightforward. After the last update from Linux Kernel 
4.19.0-10amd64 to 4.19.0-11amd64 on Debian Buster, there seems to be a sound 
input/output issue with the Headphone Jack port.

The sound comes out perfectly well through the speakers, however there is a 
complete loss of sound output and voice input when using headphones/earphones.

Reverting back to Linux Kernel 4.19.0-10amd64 when in Grub fixes the issue, 
therefore it seems to be related to the latest update?

Best regards,

Edouard H.

Re: How to disable the screen locker on amd64 buster?

[Charles Curley]

On Sat, 3 Oct 2020 04:27:08 -0400
Gene Heskett  wrote:

> The computer is controlling high powered machinery. Having the screen 
> locker kick in, disabling our access to the application until we have 
> wasted a minute typing on a poor keyboard trying to log back in can
> be quite dangerous when the machine has a runaway. Anything we do
> with xset is overridden before the 10 minute timeout is done.
> 
> Some of us like xfce4, please advise how to permanently disable
> lightdm and its light-locker. _Forever_. We do know how to turn off
> the monitor at the end of the day.
> 
> Thank you.
> 
> Cheers, Gene Heskett



-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: How to disable the screen locker on amd64 buster?

[Gene Heskett]

On Saturday 03 October 2020 08:12:56 Dan Ritter wrote:

> Gene Heskett wrote:
> > The computer is controlling high powered machinery. Having the
> > screen locker kick in, disabling our access to the application until
> > we have wasted a minute typing on a poor keyboard trying to log back
> > in can be quite dangerous when the machine has a runaway. Anything
> > we do with xset is overridden before the 10 minute timeout is done.
> >
> > Some of us like xfce4, please advise how to permanently disable
> > lightdm and its light-locker. _Forever_. We do know how to turn off
> > the monitor at the end of the day.
>
> I would try
>
> apt remove lightdm light-locker
and task-xfce, the meta installer file was also selected
> and either installing xdm or just using startx to get X11 and
> XFCE up when you want it.

Which is for me, 100% of the time, so xdm installed.

> -dsr

did that and installed xdm, reboot is next. But apt claimed there were 
several hundred packages (353 count) that could be autoremoved.  Is that 
normal after an iso install and update to 10.6? I did the autoremove, 
linuxcnc still runs, so I think we are in business. 34 minutes after the 
reboot:

gene@lathe:~$ uptime
 10:42:05 up 34 min,  1 user,  load average: 0.00, 0.16, 0.44
gene@lathe:~$ xset -q
Keyboard Control:
  auto repeat:  onkey click percent:  10LED mask:  0002
  XKB indicators:
00: Caps Lock:   off01: Num Lock:on 02: Scroll Lock: off
03: Compose: off04: Kana:off05: Sleep:   off
06: Suspend: off07: Mute:off08: Misc:off
09: Mail:off10: Charging:off11: Shift Lock:  off
12: Group 2: off13: Mouse Keys:  off
  auto repeat delay:  594repeat rate:  14
  auto repeating keys:  00ffdbbf
fadfffefffed
9fff
fff7
  bell percent:  50bell pitch:  400bell duration:  100
Pointer Control:
  acceleration:  2/1threshold:  4
Screen Saver:
  prefer blanking:  noallow exposures:  yes
  timeout:  0cycle:  0
Colors:
  default colormap:  0x20BlackPixel:  0x0WhitePixel:  0xff
Font Path:
  
/usr/share/fonts/X11/misc,/usr/share/fonts/X11/100dpi/:unscaled,/usr/share/fonts/X11/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/share/fonts/X11/100dpi,/usr/share/fonts/X11/75dpi,built-ins
DPMS (Energy Star):
  Standby: 450Suspend: 600Off: 900
  DPMS is Disabled

I believe thats what we wanted.

The above now shows blanking off, expose on, and DPMS off after the 
reboot and no one has yet logged in locally, looks good.

Thanks a bunch, Dan

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: How to disable the screen locker on amd64 buster?

[Charles Curley]

On Sat, 3 Oct 2020 04:27:08 -0400
Gene Heskett  wrote:

> Some of us like xfce4, please advise how to permanently disable
> lightdm and its light-locker. _Forever_. We do know how to turn off
> the monitor at the end of the day.

If you are running XFCE on the beastie in question:

The XFCE power manager may have an entry in the notification area. If
not, install it. Right click on that. Check "Presentation mode". All
done.

Note: I don't know how persistent that is.

-- 
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

Re: can't boot to a graphical interface.

[songbird]

Frank McCormick wrote:
> While compiling an application today my Debian bullseye system somehow 
> got messed up. It will boot to a CLI but no X, apparently because for 
> some reason the system is unable to access some files in 
> /usr/share/dbus-1. It keeps saying access denied. The directories and 
> files are owned by root, and if I noot to a CLI I have no trouble 
> accessing them using sudo and midnight commander.
>
> I tried reinstalling systemd but it ended with the same problem.
>
> Can anyone help?

  that certainly sounds strange to me.

  what application and why were you doing this as
root - seems like asking for trouble...  :)

  hmm, what is your desktop manager?  i use lightdm.
perhaps reinstall it.

  the other thing would be to check your systemd 
units to make sure something didn't get masked out
or removed that you wanted to be used for sure and
put that back into place.


  songbird

Re: How to disable the screen locker on amd64 buster?

[songbird]

Dan Ritter wrote:
...
> I would try
>
> apt remove lightdm light-locker

  i don't even know what the package light-locker is as i
don't see it here and i have lightdm installed (but i'm
running testing and bits of unstable so perhaps it's not
come by yet).

  i have a dislike for screen savers and auto anything that
interferes with my system so i've masked out some power stuff
and screen savers to keep them from getting in the way.

  it's very annoying when other people make assumptions about
how i want to do things.


> and either installing xdm or just using startx to get X11 and
> XFCE up when you want it.

  ditto!


  songbird

Re: How to disable the screen locker on amd64 buster?

[Andrew M.A. Cater]

On Sat, Oct 03, 2020 at 04:27:08AM -0400, Gene Heskett wrote:
> The computer is controlling high powered machinery. Having the screen 
> locker kick in, disabling our access to the application until we have 
> wasted a minute typing on a poor keyboard trying to log back in can be 
> quite dangerous when the machine has a runaway. Anything we do with xset 
> is overridden before the 10 minute timeout is done.
> 

Gene,

You've been asking similar questions for years on various of the Debian lists -
- real time kernel, how to do things on Raspberry Pi, generically on ARM ...

Yours is a niche case: not many of us have lathes hooked up to Linux boxes.

Have you considered not using a desktop environment at all rather than trying
to expect the rest of us to run through problems we don't understand? We're
not being collectively unintelligent but this would be easier if we could all 
get to one topic at a time :)

> Some of us like xfce4, please advise how to permanently disable lightdm 
> and its light-locker. _Forever_. We do know how to turn off the monitor 
> at the end of the day.
> 

As suggested elsewhere : remove lightdm. Maybe work out just which programs 
you _must_ run and strip down a desktop environment / an X environment to 
just run that stuff. That might  take time - and you might not be able to get
 down to nothing extraneous but it would be a start. Pencil, paper and a plan 
splitting things down to single steps or areas of concern might help 
significantly here and elsewhere.

All the best

Andy C.

> Thank you.
> 
> Cheers, Gene Heskett
> -- 
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> If we desire respect for the law, we must first make the law respectable.
>  - Louis D. Brandeis
> Genes Web page 
> 

Re: How to disable the screen locker on amd64 buster?

[Dan Ritter]

Gene Heskett wrote: 
> The computer is controlling high powered machinery. Having the screen 
> locker kick in, disabling our access to the application until we have 
> wasted a minute typing on a poor keyboard trying to log back in can be 
> quite dangerous when the machine has a runaway. Anything we do with xset 
> is overridden before the 10 minute timeout is done.
> 
> Some of us like xfce4, please advise how to permanently disable lightdm 
> and its light-locker. _Forever_. We do know how to turn off the monitor 
> at the end of the day.

I would try

apt remove lightdm light-locker

and either installing xdm or just using startx to get X11 and
XFCE up when you want it.

-dsr-

Re: Pantalla negra en OBS Studio

[Fabian Dos Santos]

Muchas gracias por las respuestas!
Mi nivel de conocimiento de Debian es algo así como 1 en una escala de 1 a
10, pero estoy aprendiendo un montón.
Nunca se tilda el sistema, todo funciona bien, vale la pena aprender a usar
Debian.
Saludos
FDS

El sáb., 3 oct. 2020 a las 3:24, Camaleón () escribió:

> El 2020-10-02 a las 10:37 -0300, Fabian Dos Santos escribió:
>
> > Necesito ayuda para grabar la pantalla de la laptop. Al utilizar
> cualquier
> > programa: vokoscreen, OBS Studio y otros, se graba el sonido pero la
> > pantalla permanece completamente negra. Ocurre lo mismo cuando quiero
> > grabar la pantalla con alguna aplicación como Zoom y otras.
>
> No indicas muchos datos sobre la configuración de tu sistema (tarjeta
> gráfica, entorno de escritorio...) pero si buscas en Google verás que
> hay mucha gente con ese problema, tanto en Vokoscreen como en OBS,
> seguramente porque ambos tiran del mismo subsistema para capturar la
> pantalla.
>
> vokoscreen no video black screen
>
> https://www.google.com/search?complete=0=en=zhZ4X6GUBYH6U77jk9AK=vokoscreen+no+video+black+screen
>
> obs no video black screen
>
> https://www.google.com/search?complete=0=en=txd4X4rYDOGRjLsPveGagAc=obs+no+video+black+screen
>
> Mira a ver si algunos de los enlaces te sirve para solucionar el
> problema en esas aplciaciones (quizá realizando algún ajuste en la
> configuración del dispositivo de captura) o prueba con otra (creo que
> VLC también graba la pantalla).
>
> Saludos,
>
> --
> Camaleón
>
>

-- 


*Fabián E. Dos SantosInstructor Asociado en Psicología Holokinética de
la Academia Internacional de Ciencias (RSM)- MéxicoCoordinador de
Actividades Académicas e Investigación - Academia Internacional de
Psicología Holokinética*


*1-Cursos, Libros, Audios, Vídeos, Reuniones, Congresos y Noticias:*

*www.percepcionunitaria.org *
*2-Tome el Curso en Psicología Holokinética por Internet (CIPH):*

*www.psicologiaholokinetica.org
**3-Libros:
"Holokinesis Libros" *

*www.holokinesislibros.com *

How to disable the screen locker on amd64 buster?

[Gene Heskett]

The computer is controlling high powered machinery. Having the screen 
locker kick in, disabling our access to the application until we have 
wasted a minute typing on a poor keyboard trying to log back in can be 
quite dangerous when the machine has a runaway. Anything we do with xset 
is overridden before the 10 minute timeout is done.

Some of us like xfce4, please advise how to permanently disable lightdm 
and its light-locker. _Forever_. We do know how to turn off the monitor 
at the end of the day.

Thank you.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: GIMP keeps crashing!

[Weaver]

On 03-10-2020 13:48, riveravaldez wrote:
> On 10/2/20, Rebecca Matthews  wrote:
>> ```
>> GNU Image Manipulation Program version 2.10.8
>> git-describe: GIMP_2_10_6-294-ga967e8d2c2
>> C compiler:
>> Using built-in specs.
>> COLLECT_GCC=gcc
>> COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
>> OFFLOAD_TARGET_NAMES=nvptx-none
>> OFFLOAD_TARGET_DEFAULT=1
>> Target: x86_64-linux-gnu
>> Configured with: ../src/configure -v --with-pkgversion='Debian 8.2.0-13'
>> --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
>> --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
>> --with-gcc-major-version-only --program-suffix=-8
>> --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
>> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
>> --libdir=/usr/lib --enable-nls --enable-clocale=gnu
>> --enable-libstdcxx-debug --enable-libstdcxx-time=yes
>> --with-default-libstdcxx-abi=new --enable-gnu-unique-object
>> --disable-vtable-verify --enable-libmpx --enable-plugin
>> --enable-default-pie --with-system-zlib --with-target-system-zlib
>> --enable-objc-gc=auto --enable-multiarch --disable-werror
>> --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
>> --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none
>> --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu
>> --host=x86_64-linux-gnu --target=x86_64-linux-gnu
>> Thread model: posix
>> gcc version 8.2.0 (Debian 8.2.0-13)

Hello Rebecca,

This could be a number of issues. 
I find some applications dive on the Enlightenment desktop, or it could
be even a hardware issue.
Sometimes software and hardware clash.
Have you checked out the bug lists, Debian and GIMP?

Kind regards,

Harry Weaver
-- 
`Religion is regarded by the common people as true,
by the wise as false,
and by the rulers as useful'.

— Lucius Annæus Seneca.

Terrorism, the new religion.

Registered Linux User: 554515

Re: [testing] noyau 5.8 => plus de sortie audio analogique

[Orion]

Bonjour,

je suis confronté au même problème (SID), mais c'est assez systématique  :
un pulseaudio -k puis pulseaudio -D ne résoud pasle pb chez moi.
je cherche une solution

en comparant la  sortie pactl info d'une fedora Fedora 32:
fedora:
Profils :
input:analog-stereo: Entrée Stéréo analogique (sinks: 0, sources: 1,
priority: 65, available: oui)
output:analog-stereo: Sortie Stéréo analogique (sinks: 1, sources: 0,
priority: 6500, available: oui)
output:analog-stereo+input:analog-stereo: Duplex stéréo analogique (sinks:
1, sources: 1, priority: 6565, available: oui)
output:iec958-stereo: Sortie Stéréo numérique (IEC958) (sinks: 1, sources:
0, priority: 5500, available: oui)
output:iec958-stereo+input:analog-stereo: Sortie Stéréo numérique (IEC958)
+ Entrée Stéréo analogique (sinks: 1, sources: 1, priority: 5565,
available: oui)

debian :
Profils :
input:analog-stereo: Entrée Stéréo analogique (sinks: 0, sources: 1,
priority: 65, available: oui)
output:iec958-stereo: Sortie Stéréo numérique (IEC958) (sinks: 1, sources:
0, priority: 5500, available: oui)
output:iec958-stereo+input:analog-stereo: Sortie Stéréo numérique (IEC958)
+ Entrée Stéréo analogique (sinks: 1, sources: 1, priority: 5565,
available: oui)

j''ai pas les profils
output:analog-stereo: Sortie Stéréo analogique (sinks: 1, sources: 0,
priority: 6500, available: oui)
output:analog-stereo+input:analog-stereo: Duplex stéréo analogique (sinks:
1, sources: 1, priority: 6565, available: oui)
sous debian, je peux les rajouter?

On Thu, Sep 24, 2020 at 9:15 PM Gaëtan Perrier 
wrote:

> Le jeudi 24 septembre 2020 à 06:54 +0200, F. Dubois a écrit :
> > Le 24/09/2020 à 01:11, Gaëtan Perrier a écrit :
> > > Bonjour,
> > >
> > > Je viens de passer en 5.8 sur ma testing et je constate que je n'ai
> plus de
> > > sortie audio analogique. Seule une sortie SPDIF est présentée ...
> > > Est-ce pareil pour vous ?
> > >
> > > Gaëtan
> >
> > Bonjour,
> >
> > Oui, c'est très aléatoire. Pulseaudio débloque complètement. Je suis en
> > Sid mais ça correspond bien, on dirait, au changement de noyau.
> >
> > Normalement un pulseaudio -k puis pulseaudio -D résout le problème...
> > jusqu'au prochain reboot.
> > Pas plus à dire, donc si il y a plus d'explications je suis preneur
> aussi.
> >
> > Fabien
> >
>
> Bonjour,
>
> Je ne sais pas si c'est lié aux mises à jours de udev et systemd
> aujourd'hui
> mais j'ai récupéré ma sortie analogique. Par contre il me semblait que
> dans le
> temps on pouvait sélectionner une config 2.0 ou 2.1 ? Maintenant c'est 5.0
> mini
> ...
>
> Gaëtan
>

Re: Pantalla negra en OBS Studio

[Camaleón]

El 2020-10-02 a las 10:37 -0300, Fabian Dos Santos escribió:

> Necesito ayuda para grabar la pantalla de la laptop. Al utilizar cualquier
> programa: vokoscreen, OBS Studio y otros, se graba el sonido pero la
> pantalla permanece completamente negra. Ocurre lo mismo cuando quiero
> grabar la pantalla con alguna aplicación como Zoom y otras.

No indicas muchos datos sobre la configuración de tu sistema (tarjeta 
gráfica, entorno de escritorio...) pero si buscas en Google verás que 
hay mucha gente con ese problema, tanto en Vokoscreen como en OBS, 
seguramente porque ambos tiran del mismo subsistema para capturar la 
pantalla.

vokoscreen no video black screen
https://www.google.com/search?complete=0=en=zhZ4X6GUBYH6U77jk9AK=vokoscreen+no+video+black+screen

obs no video black screen
https://www.google.com/search?complete=0=en=txd4X4rYDOGRjLsPveGagAc=obs+no+video+black+screen

Mira a ver si algunos de los enlaces te sirve para solucionar el 
problema en esas aplciaciones (quizá realizando algún ajuste en la 
configuración del dispositivo de captura) o prueba con otra (creo que 
VLC también graba la pantalla).

Saludos,

-- 
Camaleón 

Re: Problema instalación Debian VirtualBox

[Camaleón]

El 2020-10-02 a las 20:44 -0300, Juan Miguel Gross escribió:

> Hola! Tengo una consulta si en este lugar me pueden contestar... Estoy
> tratando de instalar Debian en  VirtualBox en Windows y al llegar a la
> parte "Instalando man-db" o algo así, se queda colgado el instalador o me
> tira un error, probé con varios ISO pero con todos es igual, que podría
> hacer?  Desde ya, muchas gracias!

¿Qué versión de Debian estás instalando?
¿Qué error te saca el instalador?
¿Comprobaste la suma de verificación de las imágenes ISO?

Que se quede colgado en man-db puede ser casualidad. O que el 
instalador llega un momento en que tiene problemas para acceder al 
medio.

Yo probaría lo siguiente:

1. Realizar una instalación mínima (sólo paquetes base, sin entorno 
gráfico ni aplicaciones), desde la mini-iso.

2. La mini-iso necesita una conexión a Internet para descargar 
paquetes, prueba a usar una réplica de red rápida y que sea cercana a tu 
ubicación.

Saludos,

-- 
Camaleón