Re: Audio broken on Lenovo ThinkPad T14 by recent upgrade on testing

[Andrei POPESCU]

On Lu, 04 ian 21, 21:57:20, Patrick Elsen wrote:
> Hey all,
> 
> I'm not sure if this is the right way or place to report this, but I've
> been running Debian bullseye (Testing) for some months now and it's
> been a really great experience, everything works out of the box
> (backlight, suspend, display brightness control, switching between
> speakers and headphones when plugged in). 
> 
> However, in a recent update, my audio has been broken. Now, I have
> three outputs that I didn't have before (labelled HDMI1, HDMI2, HDMI3),
> it doesn't recognize my internal speakers or headphones anymore,
> meaning that audio playback is completely broken.

What does 'aplay -l' and 'aplay -L' show?

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: problemas con crontab

[Camaleón]

El 2021-01-04 a las 19:05 -0300, Fernando Romero escribió:

> Estoy usando Debian 10 y tengo problemas con el horario en crontab, estoy
> corriendo un php con curl a cierto horario, pero siempre se ejecuta 4
> minutos mas tarde, es como que crontab no toma la hora del servidor y esta
> usando un horario propio.
> A alguien le paso esto?

¿Sólo te pasa el desfase de 4 minutos con esa rutina?

Prueba a crear otra que ejecute alguna orden sencilla, de bash, para 
ver si sucede lo mismo.

El desfase es muy corto como para pensar en un problema con el ajuste 
de la hora (supongo que tendrás el sistema sincronizado con un servidor 
NTP) o que se trate de una mala configuración de la zona horaria (el 
desfase sería de medias horas u horas).

Sólo un apunte: una cosa es la hora a la que se ejecuta la rutina (que 
debe ser exactamente a la que la has programado en el crontab) y otra 
cosa es lo que haga esa rutina y cuándo lo ejecute, que se puede 
demorar dependiendo de lo que tenga que ejecutar (si es php+curl me 
suena a que debe haber un servidor web de por medio que lleve su 
propio registro/configuración horaria).

Saludos,

-- 
Camaleón 

Re: Nvidia Optimus, Debian 10, and Firefox ESR crashes

[Andrei POPESCU]

On Lu, 04 ian 21, 19:47:18, David Christensen wrote:
> On 2021-01-04 09:14, Alexander V. Makartsev wrote:
> > > 
> > "xrandr" utility should help you with diagnostics and setup:
> >      $ xrandr -q
> 
> 2021-01-04 19:22:57 root@dipsy ~
> # xrandr -q
> Can't open display

The '$' in the post above means it should be run from a user account, 
preferably within the X session.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Nvidia Optimus, Debian 10, and Firefox ESR crashes

[Felix Miata]

David Christensen composed on 2021-01-04 19:47 (UTC-0800):

> And a new issue:

> Xfce -> Settings -> Display -> Resolution now only offers three choices:

> 1024x768
> 800x600
> 640x480

> The laptop has a 1920x1080 screen.  The external monitor is 1920x1080. 
> The nouveau driver was able to drive both the laptop display and the 
> external monitor at 1920x1080.  I would like to do so with the non-free 
> Nvidia legacy driver.

Installation of a proprietary driver typically entailing several changes from a
default installation. Typically one such change is a cmdline option, either
nomodeset, or nouveau.modeset=0 in the case of NVidia GPUs. KMS, which these
options disable, is required to support all competent FOSS DDX drivers. The
fallbacks typically are limited to VESA modes, which AFAIK normally do not 
include
1920x1080, which you wouldn't want to use except in emergency anyway, as they
offer nothing resembling acceleration. Restoring a normal cmdline may fix you 
up.
It may not, as some uninstallation processes fail to remove a library altered to
accommodate the proprietaryware. People with this problem often choose to
reinstall the OS because all the help they get suggesting a fix fails them.

See also:

-- 
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: Nvidia Optimus, Debian 10, and Firefox ESR crashes

[David Christensen]

On 2021-01-04 09:14, Alexander V. Makartsev wrote:

On 04.01.2021 09:31, David Christensen wrote:


Reboot -- boots okay -- login manager displayed -- login okay -- Xfce 
desktop okay -- external monitor not getting signal.



Xfce -> Settings -> Display only lists one monitor "default":

Resolution    1920x1080 (or 640x480)
Refresh rate    0.0
Rotation    None
Reflection    None


How do I get the external monitor working?


David


"xrandr" utility should help you with diagnostics and setup:
     $ xrandr -q


Thank you for the reply.  :-)


2021-01-04 19:22:57 root@dipsy ~
# xrandr -q
Can't open display



Additional info:
     $ xrandr --listproviders


2021-01-04 19:23:00 root@dipsy ~
# xrandr --listproviders
Can't open display



     $ glxinfo | grep -e 'glx' -e 'OpenGL' -e 'display'


2021-01-04 19:25:06 root@dipsy ~
# glxinfo | grep -e 'glx' -e 'OpenGL' -e 'display'
-bash: glxinfo: command not found

2021-01-04 19:26:07 root@dipsy ~
# apt-cache search glxinfo
mesa-utils - Miscellaneous Mesa GL utilities

2021-01-04 19:26:28 root@dipsy ~
# apt-get install mesa-utils
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  libglew2.1
Suggested packages:
  glew-utils
The following NEW packages will be installed:
  libglew2.1 mesa-utils
0 upgraded, 2 newly installed, 0 to remove and 4 not upgraded.
Need to get 196 kB of archives.
After this operation, 1000 kB of additional disk space will be used.
Do you want to continue? [Y/n]


2021-01-04 19:26:39 root@dipsy ~
# glxinfo | grep -e 'glx' -e 'OpenGL' -e 'display'
Error: unable to open display


Perhaps "nvidia-settings" utility could be a fastest way to configure 
dual-monitor setup and generate config file for Xorg to make settings 
permanent.


2021-01-04 19:29:08 root@dipsy ~
# nvidia-settings
-bash: nvidia-settings: command not found


2021-01-04 19:29:19 root@dipsy ~
# apt-get install nvidia-settings
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  nvidia-alternative nvidia-legacy-check
Recommended packages:
  libgl1-nvidia-glvnd-glx | libgl1-nvidia-glx nvidia-vdpau-driver
  libnvidia-ml1
The following NEW packages will be installed:
  nvidia-alternative nvidia-legacy-check nvidia-settings
0 upgraded, 3 newly installed, 0 to remove and 4 not upgraded.
Need to get 1393 kB of archives.
After this operation, 3787 kB of additional disk space will be used.
Do you want to continue? [Y/n]



Note pop-up:

 ┌┤ Configuring nvidia-legacy-check 
├┐
 │ 
 │
 │ This system has a graphics card which is no longer handled by the 
NVIDIA  │
 │ driver (package nvidia-driver). You may wish to keep the package 
 │
 │ installed - for instance to drive some other card - but the card 
with │
 │ the following chipset won't be usable: 
 │
 │ 
 │
 │ 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119M 
[NVS  │
 │ 4200M] [10de:1056] (rev a1) 
 │
 │ 
 │
 │ The above card requires either the non-free legacy NVIDIA driver 
 │
 │ (package nvidia-legacy-390xx-driver) or the free Nouveau driver 
(package  │
 │ xserver-xorg-video-nouveau). 
 │
 │ 
 │
 │ Use the update-glx command to switch between different installed 
 │
 │ drivers. 
 │
 │ 
 │
 │ Before the Nouveau driver can be used you must remove NVIDIA 
 │
 │ configuration from xorg.conf (and xorg.conf.d/). 
 │
 │ 
 │
 │ Install NVIDIA driver despite unsupported graphics card? 
 │
 │ 
 │
 │
 │


Choose 'No'.


And a new issue:

Xfce -> Settings -> Display -> Resolution now only offers three choices:

1024x768
800x600
640x480


The laptop has a 1920x1080 screen.  The external monitor is 1920x1080. 
The nouveau driver was able to drive both the laptop display and the 
external monitor at 1920x1080.  I would like to do so with the non-free 
Nvidia legacy driver.



Looking around for X configuration files:

2021-01-04 19:34:58 root@dipsy ~
# locate xorg.conf
/usr/share/X11/xorg.conf.d
/usr/share/X11/xorg.conf.d/10-amdgpu.conf
/usr/share/X11/xorg.conf.d/10-quirks.conf
/usr/share/X11/xorg.conf.d/10-radeon.conf
/usr/share/X11/xorg.conf.d/40-libinput.conf
/usr/share/X11/xorg.conf.d/70-wacom.conf
/usr/share/X11/xorg.conf.d/nvidia-drm-outputclass.conf
/usr/share/doc/xserver-xorg-video-intel/xorg.conf
/usr/share/man/man5/xorg.conf.5.gz
/usr/share/man/man5/xorg.conf.d.5.gz


RTFM xorg.conf(5), I am unsure if any of the located files (above) are 
active:


   Xorg uses a configuration file called xorg.conf and files ending 
in the
   suffix .conf from the directory xorg.conf.d for its initial 
setup.  The
   xorg.conf configuration file is searched for in  the  following 
places

   when the server is started as a normal user:

   

Re: Audio broken on Lenovo ThinkPad T14 by recent upgrade on testing

[黃炳熙]

Patrick Elsen  writes:

> Hey all,
>
> I'm not sure if this is the right way or place to report this, but I've
> been running Debian bullseye (Testing) for some months now and it's
> been a really great experience, everything works out of the box
> (backlight, suspend, display brightness control, switching between
> speakers and headphones when plugged in). 
>
> However, in a recent update, my audio has been broken. Now, I have
> three outputs that I didn't have before (labelled HDMI1, HDMI2, HDMI3),
> it doesn't recognize my internal speakers or headphones anymore,
> meaning that audio playback is completely broken.
>
> I don't know what package specfically is responsible, but I have
> attached the /var/log/apt/history.log entry that was the update that I
> think bricked things. I can provide more logs and information if
> needed.
>
> My guess would be that alsa-topology-conf or alsa-ucm-conf are the
> culprit, because those two are the only ones I see that are related to
> sound and audio things?
>
> Maybe someone here can help me or look into it.

Dear Patrick,

Please forgive me to say off-topic.

At past days, me also did try to hard linux install. Especially i always
did fail to setup device driver correctly. So someday i did make chage
the strategy. Chromebook is already to finished them. So i don't have
the stress to setup drivers in linux installation. Then i only have to
just software such as emacs, firefox, gitlab, etc, ...

So i am happy now with no-stress furthermore i have plan to buy new
thinkpad-chromebook [zork-morphius]. At there i will install the great
*Bullseye*.

(currently i am on Ubuntu 18.04 under chromebook [oak-birch])

Sincerely, Linux fan Byung-Hee

-- 
^고맙습니다 _救濟蒼生_ 감사합니다_^))//

Re: Label printer Debian compatible

[rhkramer]

On Monday, January 04, 2021 07:29:29 PM Tom Browder wrote:
> I do the same, except I create a new pdf with only the necessary cells
> printed. But it's a laser printer so it does gray the paper a bit. But
> great point on the inkjet. That may be the best option: an inexpensive b
> inkjet.

Considering Walmart was selling a Canon inkjet for $19,95 on black Friday, 
yeah it is an inexpensive option.  (I think Walmart's regular price for that 
inkjet is $40.)

> Thanks!

You're welcome!

Re: Label printer Debian compatible

[Tom Browder]

On Mon, Jan 4, 2021 at 17:05  wrote:

> On Monday, January 04, 2021 01:37:19 PM Joe Pfeiffer wrote:
> > Tom Browder  writes:
> > > Has anyone had any success driving a mailing label printer for mailing
> > > labels from either a LAN or direct connection with a Linux box?
> > >
> > > I can print sheets of mailing labels from my main printer, but I would
> > > love to be able to print single labels from my adress db with a
> suitable
> > > specialty printer and a suitable Linux driver.
>
> What I do is use sheets with multiple labels per sheets, but then only put
> text on a template (in officewriter) for the labels I need.  Then when I
> need
> more, I erase that text, add text for the labels not yet printed, and run
> the
> sheet though my printer again.


I do the same, except I create a new pdf with only the necessary cells
printed. But it's a laser printer so it does gray the paper a bit. But
great point on the inkjet. That may be the best option: an inexpensive b
inkjet.

Thanks!

-Tom

Re: Label printer Debian compatible

[rhkramer]

On Monday, January 04, 2021 01:37:19 PM Joe Pfeiffer wrote:
> Tom Browder  writes:
> > Has anyone had any success driving a mailing label printer for mailing
> > labels from either a LAN or direct connection with a Linux box?
> > 
> > I can print sheets of mailing labels from my main printer, but I would
> > love to be able to print single labels from my adress db with a suitable
> > specialty printer and a suitable Linux driver.

What I do is use sheets with multiple labels per sheets, but then only put 
text on a template (in officewriter) for the labels I need.  Then when I need 
more, I erase that text, add text for the labels not yet printed, and run the 
sheet though my printer again.

That works fine on an inkjet printer, it probably would not work on a laser 
printer because heating the sheet of labels each time might damage / 
deteriorate the labels.

problemas con crontab

[Fernando Romero]

Hola como estan.
Estoy usando Debian 10 y tengo problemas con el horario en crontab, estoy
corriendo un php con curl a cierto horario, pero siempre se ejecuta 4
minutos mas tarde, es como que crontab no toma la hora del servidor y esta
usando un horario propio.
A alguien le paso esto?

Saludos

Audio broken on Lenovo ThinkPad T14 by recent upgrade on testing

[Patrick Elsen]

Hey all,

I'm not sure if this is the right way or place to report this, but I've
been running Debian bullseye (Testing) for some months now and it's
been a really great experience, everything works out of the box
(backlight, suspend, display brightness control, switching between
speakers and headphones when plugged in). 

However, in a recent update, my audio has been broken. Now, I have
three outputs that I didn't have before (labelled HDMI1, HDMI2, HDMI3),
it doesn't recognize my internal speakers or headphones anymore,
meaning that audio playback is completely broken.

I don't know what package specfically is responsible, but I have
attached the /var/log/apt/history.log entry that was the update that I
think bricked things. I can provide more logs and information if
needed.

My guess would be that alsa-topology-conf or alsa-ucm-conf are the
culprit, because those two are the only ones I see that are related to
sound and audio things?

Maybe someone here can help me or look into it.

Cheers,
-Patrick
Start-Date: 2020-12-27  23:06:21
Commandline: apt upgrade
Requested-By: patrick (1000)
Install: libdeflate0:amd64 (1.6-1, automatic), libadwaitaqtpriv1:amd64 
(1.2.0-2, automatic), llvm-11-runtime:amd64 (1:11.0.0-5+b1, automatic), 
libges-1.0-0:amd64 (1.18.2-1, automatic), libgit2-1.1:amd64 (1.1.0+dfsg.1-2, 
automatic), liblist-moreutils-xs-perl:amd64 (0.430-2, automatic), 
containerd:amd64 (1.4.3~ds1-1, automatic), libboost-locale1.74.0:amd64 
(1.74.0-3+b1, automatic), libadwaitaqt1:amd64 (1.2.0-2, automatic), 
llvm-11-dev:amd64 (1:11.0.0-5+b1, automatic), gedit-plugin-text-size:amd64 
(3.38.1-1, automatic), libplymouth5:amd64 (0.9.5-2, automatic), 
libxkbregistry0:amd64 (1.0.3-2, automatic), clang-format-11:amd64 
(1:11.0.0-5+b1, automatic), ruby-rubygems:amd64 (3.2.0~rc.2-5, automatic), 
llvm-11-tools:amd64 (1:11.0.0-5+b1, automatic), linux-image-5.9.0-5-amd64:amd64 
(5.9.15-1, automatic), llvm-11:amd64 (1:11.0.0-5+b1, automatic)
Upgrade: speech-dispatcher-espeak-ng:amd64 (0.10.2-1, 0.10.2-2), 
gir1.2-lokdocview-0.1:amd64 (1:7.0.3-4+b1, 1:7.0.4~rc2-1+b1), 
speech-dispatcher-audio-plugins:amd64 (0.10.2-1, 0.10.2-2), fdisk:amd64 
(2.36.1-2, 2.36.1-3), alsa-topology-conf:amd64 (1.2.3-1, 1.2.4-1), 
texlive-plain-generic:amd64 (2020.20200925-1, 2020.20201129-2), 
node-os-locale:amd64 (4.0.0-1, 5.0.0-1), libjson-glib-1.0-0:amd64 (1.6.0-1, 
1.6.0-2), libxencall1:amd64 (4.14.0+80-gd101b417b7-1, 4.14.0+88-g1d1d1f5391-2), 
manpages:amd64 (5.09-2, 5.10-1), perl-base:amd64 (5.32.0-5, 5.32.0-6), 
init:amd64 (1.59, 1.60), libreoffice-math:amd64 (1:7.0.3-4+b1, 
1:7.0.4~rc2-1+b1), init-system-helpers:amd64 (1.59, 1.60), libssh2-1:amd64 
(1.8.0-2.1, 1.9.0-2), node-resolve:amd64 (1.19.0+~cs4.20.2-1, 
1.19.0+~cs5.20.8-2), aspell-pt-pt:amd64 (20201103-2, 20201212-1), 
libgovirt2:amd64 (0.3.7-1, 0.3.7-2), python3-pyside2.qtwidgets:amd64 
(5.15.0-5+b1, 5.15.0-6), liblibreoffice-java:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1), 
fonts-lyx:amd64 (2.3.5.2-1, 2.3.6-1), bsdextrautils:amd64 (2.36.1-2, 2.36.1-3), 
python3-cupshelpers:amd64 (1.5.12-1, 1.5.13-1), texlive-metapost-doc:amd64 
(2020.20200925-1, 2020.20201203-2), texlive-font-utils:amd64 (2020.20201129-1, 
2020.20201129-2), texlive-lang-spanish:amd64 (2020.20200925-2, 
2020.20201129-1), libseccomp2:amd64 (2.5.0-3+b1, 2.5.1-1), 
util-linux-locales:amd64 (2.36.1-2, 2.36.1-3), libencode-locale-perl:amd64 
(1.05-1, 1.05-1.1), texlive-publishers-doc:amd64 (2020.20201129-1, 
2020.20201129-2), uno-libs-private:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1+b1), 
libao4:amd64 (1.2.2+20180113-1+b1, 1.2.2+20180113-1.1), libaudit-common:amd64 
(1:2.8.5-3.1, 1:3.0-1), uim-data:amd64 (1:1.8.8-6.1, 1:1.8.8-7), 
adwaita-qt:amd64 (1.1.4-1, 1.2.0-2), uim-fep:amd64 (1:1.8.8-6.1+b2, 1:1.8.8-7), 
texlive-latex-base:amd64 (2020.20200925-1, 2020.20201203-2), uuid-runtime:amd64 
(2.36.1-2, 2.36.1-3), libquvi-scripts-0.9:amd64 (0.9.20131130-1.1, 
0.9.20131130-1.2), libqt5multimediagsttools5:amd64 (5.15.1-2, 5.15.2-2), 
python3-zope.interface:amd64 (5.1.2-1, 5.1.2-1+b1), iportuguese:amd64 
(20201103-2, 20201212-1), libfdisk1:amd64 (2.36.1-1, 2.36.1-3), 
publicsuffix:amd64 (20200729.1725-1, 20201215.0006-1), javascript-common:amd64 
(11, 11+nmu1), libauthen-sasl-perl:amd64 (2.1600-1, 2.1600-1.1), 
libdrm-nouveau2:amd64 (2.4.103-1, 2.4.103-2), osinfo-db:amd64 (0.20201119-1, 
0.20201218-1), hunspell-fr:amd64 (1:6.4.1-1, 1:7.0-1), 
libreoffice-l10n-zh-cn:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1), libridl-java:amd64 
(1:7.0.3-4, 1:7.0.4~rc2-1), node-jquery:amd64 (3.5.1+dfsg+~3.5.4-2, 
3.5.1+dfsg+~3.5.4-3), librygel-renderer-gst-2.6-2:amd64 (0.38.3-1, 0.40.0-1), 
libreoffice-l10n-zh-tw:amd64 (1:7.0.3-4, 1:7.0.4~rc2-1), linux-libc-dev:amd64 
(5.9.9-1, 5.9.15-1), liblist-moreutils-perl:amd64 (0.416-1+b6, 0.430-2), 
libxml-sax-base-perl:amd64 (1.09-1, 1.09-1.1), libpython3.8-dev:amd64 (3.8.6-1, 
3.8.7-1), llvm:amd64 (1:9.0-49.1, 1:11.0-51+nmu1), alsa-ucm-conf:amd64 
(1.2.3-1, 1.2.4-1), feynmf:amd64 (1.08-11, 1.08-12), 

Re: Label printer Debian compatible

[Joe Pfeiffer]

Tom Browder  writes:

> On Mon, Jan 4, 2021 at 12:57 PM Joe Pfeiffer  wrote:
>> I have had good success with a Dymo LabelWriter 450.
>
> USB connection?

Yes.

Re: AMD Radeon 6490M

[Felix Miata]

Andrei POPESCU composed on 2021-01-04 21:45 (UTC+0200):

> On Lu, 04 ian 21, 18:51:58, Hans wrote:

>> What is not existent, can not be loaded. :)

> An initramfs rebuild is still needed, maybe that's the reason.

This is why I suggested to test first via radeon.modeset=0. Blacklist means 
don't
load the radeon kernel module, which is what radeon.modeset=0 causes.
-- 
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: Label printer Debian compatible

[deloptes]

Tom Browder wrote:

> On Mon, Jan 4, 2021 at 12:57 PM Joe Pfeiffer  wrote:
>> I have had good success with a Dymo LabelWriter 450.
> 
> USB connection?

yes

Re: AMD Radeon 6490M

[Felix Miata]

LuKaRo composed on 2021-01-04 17:58 (UTC+0100):

> Felix Miata wrote:

> I'd be comfortable with blacklisting the NVidia graphics and just using the
> Intel one for example. I just don't know how to do this. Maybe with some kind
> of special Xorg config?

Try appending to the kernel command line in Grub:

radeon.modeset=0

This will disable KMS for the ATI GPU only, leaving it enabled for the Intel.
If it doesn't help, upload Xorg.0.log again.

> Xorg.0.log: https://termbin.com/x15x dmesg:
> https://termbin.com/uc85

Your Xorg.0.log suggests you may have conflicts somewhere in /etc/X11/xorg.con*.
If xorg.conf or files in xorg.conf.d/ contain sections for Device, Monitor 
and/or
Screen, try removing such files. Uploading any that exist might explain what's
been happening or not.

What bothers me most about the log is the string "ntel" does not appear in
it. Second place, in dmesg I recognize only two strings containing ntel that
apply to video.
-- 
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: AMD Radeon 6490M

[Andrei POPESCU]

On Lu, 04 ian 21, 18:51:58, Hans wrote:
> Am Montag, 4. Januar 2021, 18:42:14 CET schrieb Andrei POPESCU:
> > 
> > An entry like
> > 
> > blacklist radeon
> > 
> > in a file under /etc/modprobe.d/ ending in '.conf' should achieve the
> > same result.
> 
> Thought of this, too, and agree! However, I had had the problem, that 
> although 
> I blacklisted it that time, the module was still loaded somehow. Ok, this was 
> long time ago, almost 2 or 3 years ago, and maybe that was just chance 
> (random?). 
> 
> What is not existent, can not be loaded. :)

An initramfs rebuild is still needed, maybe that's the reason.

Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: Label printer Debian compatible

[Tom Browder]

On Mon, Jan 4, 2021 at 12:57 PM Joe Pfeiffer  wrote:
> I have had good success with a Dymo LabelWriter 450.

USB connection?

Re: Label printer Debian compatible

[Joe Pfeiffer]

Tom Browder  writes:

> Has anyone had any success driving a mailing label printer for mailing labels 
> from either a LAN or direct connection with a Linux box? 
>
> I can print sheets of mailing labels from my main printer, but I would love 
> to be able to print single labels from my adress db with a suitable specialty 
> printer and a suitable Linux driver.
>
> Thanks, and Happy New Year to all!

I have had good success with a Dymo LabelWriter 450.

Re: Bullseye: setting and using $DISPLAY after su -

[Charles Curley]

On Mon, 4 Jan 2021 07:25:30 -0500
Greg Wooledge  wrote:

> > Today is Setting Orange, the 73rd of The Aftermath, 3186. All Hail
> > Discordia! root@hawk:~# env | grep DISPLAY
> > DISPLAY=:0  
> 
> Clearly you're doing something special in root's .profile -- at the
> very least, you're running that ddate command.  Is it possible you're
> also hard-coding something like 'export DISPLAY=:0' there?
> 
> > root@hawk:~# xclock &
> > [1] 3550
> > root@hawk:~# 
> > 
> > (xclock ran successfully.)  
> 
> Is it possible you also hard-coded something like
> 'export XAUTHORITY=/home/charles/.Xauthority' in root's .profile?
> 

Good thoughts, both. But, no such luck. I also checked the /etc
equivalents, and others mentioned in man bash, and found none such.

However, in the course of doing that I noticed that .Xauthority is now
a regular file, owned by root:root and 0600, as it should be. The date
on it is earlier this morning, when I logged in via SSH from another
machine. With the su alias I described earlier, xclock works.

-- 
Does anybody read signatures any more?

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

Re: AMD Radeon 6490M

[Hans]

Am Montag, 4. Januar 2021, 18:42:14 CET schrieb Andrei POPESCU:

Thought of this, too, and agree! However, I had had the problem, that although 
I blacklisted it that time, the module was still loaded somehow. Ok, this was 
long time ago, almost 2 or 3 years ago, and maybe that was just chance 
(random?). 

What is not existent, can not be loaded. :)

Have fun, good luck and happy hacking!

Kind regards

Hans




> 
> An entry like
> 
> blacklist radeon
> 
> in a file under /etc/modprobe.d/ ending in '.conf' should achieve the
> same result.
> 
> 
> Kind regards,
> Andrei

Re: AMD Radeon 6490M

[Andrei POPESCU]

On Lu, 04 ian 21, 18:36:29, Hans wrote:
> Am Montag, 4. Januar 2021, 17:58:56 CET schrieb LuKaRo:
> 
> Hello,
> 
> the other way is just to delete or move away the radeon* modules from /lib/
> modules/kernel*version/ and rebuild initramfs again.
> 
> Did help me in the past with a corrupted nvidia-module.

An entry like

blacklist radeon

in a file under /etc/modprobe.d/ ending in '.conf' should achieve the 
same result.


Kind regards,
Andrei
-- 
http://wiki.debian.org/FAQsFromDebianUser


signature.asc
Description: PGP signature

Re: AMD Radeon 6490M

[Hans]

Am Montag, 4. Januar 2021, 17:58:56 CET schrieb LuKaRo:

Hello,

the other way is just to delete or move away the radeon* modules from /lib/
modules/kernel*version/ and rebuild initramfs again.

Did help me in the past with a corrupted nvidia-module.

Hope this helps.

Best regards

Hans


> On 04.01.21 04:28, Felix Miata wrote:
> > You may be able to disable the Radeon indirectly adding this to the kernel
> > command> 
> > line in Grub:
> > radeon.modeset=0
> > 
> > I suspect doing this could functionally make the Intel GPU preferred.
> 
> Thanks! Unfortunately, this didn't help :/



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

Re: AMD Radeon 6490M

[deloptes]

LuKaRo wrote:

> I'd be comfortable with blacklisting the NVidia graphics and just using
> the Intel one for example. I just don't know how to do this. Maybe with
> some kind of special Xorg config?

nowdays Xorg does automatic configuration. You could bypass this by saving
the configuration adjusting it to your needs and installing
as /etc/X11/xorg.conf

$ man xorg.conf 

$ man Xorg
[...]
   -configure
   When this option is specified, the Xorg server loads all
video driver modules, probes for available hardware, and writes out an 
initial
   xorg.conf(5) file based on what was detected.  This option
currently has some problems on some platforms, but in most cases it is a
good
   way to bootstrap the configuration process.  This option is
only available when the server is run as root (i.e, with real-uid 0).

there are many examples on the internet

Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch

[deloptes]

Dan Ritter wrote:

> If you absolutely need a working camera as soon as possible, buy
> a new USB camera.

but the subject says it is integrated. I suggest just install a new kernel
(may be from back ports if available and you want to stay on stretch)
you can compile new kernel or simply upgrade to buster.

Re: Nvidia Optimus, Debian 10, and Firefox ESR crashes

[Alexander V. Makartsev]

On 04.01.2021 09:31, David Christensen wrote:


Reboot -- boots okay -- login manager displayed -- login okay -- Xfce 
desktop okay -- external monitor not getting signal.



Xfce -> Settings -> Display only lists one monitor "default":

Resolution    1920x1080 (or 640x480)
Refresh rate    0.0
Rotation    None
Reflection    None


How do I get the external monitor working?


David


"xrandr" utility should help you with diagnostics and setup:
    $ xrandr -q

Additional info:
    $ xrandr --listproviders
    $ glxinfo | grep -e 'glx' -e 'OpenGL' -e 'display'

Perhaps "nvidia-settings" utility could be a fastest way to configure 
dual-monitor setup and generate config file for Xorg to make settings 
permanent.
I don't use dual-monitor setup myself, so I can't get you a clean 
example of how to configure it.


--
With kindest regards, Alexander.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄

Re: AMD Radeon 6490M

[LuKaRo]

On 04.01.21 04:28, Felix Miata wrote:
> You may be able to disable the Radeon indirectly adding this to the kernel 
> command
> line in Grub:
>
>   radeon.modeset=0
>
> I suspect doing this could functionally make the Intel GPU preferred.
Thanks! Unfortunately, this didn't help :/

Re: AMD Radeon 6490M

[LuKaRo]

On 04.01.21 04:24, Felix Miata wrote:
> LuKaRo composed on 2021-01-04 03:24 (UTC+0100):
>
> Did you check to see if there is a way in the BIOS to disable the Radeon?
Unfortunately, no, because this is a MacBook, and Apple does not allow such 
settings
> Getting "dual graphics" or "hybrid graphics" going on a laptop is a common
> problem. I don't have any, but I see a lot of threads about getting them 
> going.
> With Intel and NVidia together, this is called "Optimus".
I'd be comfortable with blacklisting the NVidia graphics and just using the 
Intel one for example. I just don't know how to do this. Maybe with some kind 
of special Xorg config?
> Your 6490M is a "Terascale" class Radeon, so don't let anything you might read
> about "Southern Islands" or "Sea Islands" waste your time.
>
> Start with a read of this driver primer (which applies to all distros, not 
> just
> openSUSE), to avoid potential confusion when you see the word "driver":
> .
> You may wish to try a bit of what you find there.
Thanks for the tip, it was a good read!
> Try hitting escape as soon as the screen goes black. Do you get a stream of 
> text
> messages? If yes, do you see any clues? You can make the messages more 
> permanent
> by reconfiguring in /etc/default/grub's GRUB_CMDLINE_LINUX_DEFAULT= line to
> exclude quiet and changing splash=silent to splash=verbose or omitting it
> altogether, possibly needing instead or in addition one of the following:
>
>   noplymouth
>   plymouth=0
>   plymouth.enable=0
The initramfs does not even work when the amd firmware is installed, e.g. I 
don't even get the password prompt for my encrypted rootfs which is the first 
step in the boot procedure. Pressing escape doesn't give any additional 
information, either.
> Sending /var/log/Xorg.0.log to http://paste.debian.net/ or 
> http://pastbin.com/ if
> it exists, or ~/.local/share/xorg/Xorg.0.log if it exists, will help us help 
> you
> if examining it yourself doesn't enable you to find a solution on your own.

I'm not sure if it got stripped by the mailing list, but both dmesg and 
Xorg.0.log were included in my previous mail. I'll link them in plain text, 
hopefully that works :) Xorg.0.log: https://termbin.com/x15x dmesg: 
https://termbin.com/uc85

Thanks for your help so far! Kind regards,

LuKaRo

Re: /bin/sh naar bash i.p.v. dash linken

[Geert Stappers]

On Mon, Jan 04, 2021 at 05:36:07PM +0200, Wouter Verhelst wrote:
> On Sun, Dec 27, 2020 at 07:15:02PM +0100, Geert Stappers wrote:
> > On Sat, Dec 26, 2020 at 09:13:23PM +0200, Wouter Verhelst wrote:
> [...]
> > > De reden dat /bin/sh naar dash verwijst, en niet naar bash, is omdat:
> > > 
> > > - dash sneller opstart,
> > > - je als je /bin/sh zegt, je alleen commando's zou mogen gebruiken die
> > >   effectief door POSIX als onderdeel van de sh interface gedefinieerd is
> > >   en er dus geen verschil zou mogen zijn,
> > > 
> > > Het gebruik van bash-specifieke functies in een /bin/sh script is niet
> > > portable. Op elk systeem dat een andere shell gebruikt dan bash als
> > > /bin/sh zal dat niet werken.
> > 
> > Hoe dat kan?   bash is tien keer groter dan dash?
> 
> Dat ondersteunt mijn eerste punt.
> 
> Ik begrijp niet goed wat je vraag is? Of bevestig je gewoon wat ik zeg?


Bevestiging.  En de "vraag" was een ongeluk.:-/


De 
> > Hoe dat kan?   bash is tien keer groter dan dash?
was bedoelt als
> > Hoe dat kan?   bash is tien keer groter dan dash!




Groeten
Geert Stappers
-- 
Communicatie:  Misverstanden oplossen

Re: 'apt upgrade' doet iets anders dan 'apt-get upgrade'

[Wouter Verhelst]

On Sat, Jan 02, 2021 at 12:46:02AM +0100, Cecil Westerhof wrote:
> Ik weet het niet 100% zeker, maar volgens mij gebeurd dit pas sinds
> kort. Er staat me bij dat apt van de week is geupdated.

Neen, is niet sinds kort. Is altijd al zo geweest.

Het verschil is dat "apt-get upgrade" nooit nieuwe pakketten zal
installeren als er een nieuwe dependency bijkomt, terwijl "apt upgrade"
dat wel kan doen. Pakketten verwijderen is iets wat beide nooit zullen
doen.

"apt dist-upgrade" en "apt-get dist-upgrade" liggen wel dichter bij
elkaar.

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard

Re: /bin/sh naar bash i.p.v. dash linken

[Wouter Verhelst]

On Sun, Dec 27, 2020 at 07:15:02PM +0100, Geert Stappers wrote:
> On Sat, Dec 26, 2020 at 09:13:23PM +0200, Wouter Verhelst wrote:
[...]
> > De reden dat /bin/sh naar dash verwijst, en niet naar bash, is omdat:
> > 
> > - dash sneller opstart,
> > - je als je /bin/sh zegt, je alleen commando's zou mogen gebruiken die
> >   effectief door POSIX als onderdeel van de sh interface gedefinieerd is
> >   en er dus geen verschil zou mogen zijn,
> > 
> > Het gebruik van bash-specifieke functies in een /bin/sh script is niet
> > portable. Op elk systeem dat een andere shell gebruikt dan bash als
> > /bin/sh zal dat niet werken.
> 
> Hoe dat kan?   bash is tien keer groter dan dash?

Dat ondersteunt mijn eerste punt.

Ik begrijp niet goed wat je vraag is? Of bevestig je gewoon wat ik zeg?

> " $ ls -l $(which bash) $(which dash)
> " -rwxr-xr-x 1 root root 1254856  4 nov 18:01 /bin/bash
> " -rwxr-xr-x 1 root root  125560 12 nov 08:58 /bin/dash
>  
> > FreeBSD heeft in de default configuratie bijvoorbeeld bash zelfs niet
> > geïnstalleerd staan.
> > 
> > Op macOS is de default shell lang bash geweest, maar dat is nooit
> > geüpgradet geweest toen bash naar GPLv3 gegaan is (dus de default bash
> > op macOS is nu wel *heel* erg oud), en ze zijn daar recent op zsh
> > overgestapt.
> > 
> > Het "probleem" dat /bin/sh niet bash is, is dus zeker niet
> > Debian-specifiek.
> > 
> > Bij Debian is op een bepaald moment de symlink van bash naar dash
> > verplaatst geweest. Dat is expliciet gelimiteerd op de versie-overgang
> > waarbij dat aangezet is. Het is dus maar één keer, en het terugzetten is
> > ook een ondersteunde configuratie (i.e., als je dat nodig hebt mag je
> > het gewoon doen).
> 
> De pijn van het terugzetten komt pas als je het shell script wat
> voor jou werkt ( want /bin/sh link naar /bin/bash verbergt bashism features) 
> niet werkt voor de ander ( want /bin/sh link naar /bin/dash )

Het is natuurlijk zo dat als je een script draait dat bashismen
gebruikt, het enkel onder bash werkt. Maar als je dat niet doet, dan zou
het zowel onder dash als onder bash moeten werken.

En als je #!/bin/sh gebruikt in het begin van je script, dan zeg je
eigenlijk dat je probeert om met elke /bin/sh te werken, en dan maakt
het ook niet uit welke sh-implementatie je gebruikt.

-- 
To the thief who stole my anti-depressants: I hope you're happy

  -- seen somewhere on the Internet on a photo of a billboard

Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch

[Dan Ritter]

Ottavio Caruso wrote: 
> https://paste.debian.net/plainh/1c22d1aa

Your kernel believes you have two video cameras, one named
Trust. They have different USB ids.

They both get recognized repeatedly in your snippet, but because
there is not enough context, I can't tell whether that means

- you put the laptop to sleep/wake.

- the cameras were unplugged/replugged.

- the kernel had an oops.

If you absolutely need a working camera as soon as possible, buy
a new USB camera. 

-dsr-

Re: [SOLUTION] Re: Bullseye: setting and using $DISPLAY after su -

[tomas]

On Mon, Jan 04, 2021 at 08:36:09AM -0500, Greg Wooledge wrote:
> On Mon, Jan 04, 2021 at 07:48:03AM -0500, The Wanderer wrote:
> > I parsed the preceding conversation as indicating that
> > 
> > $ ln -sf /home/auser/.Xauthority /root/.Xauthority
> > 
> > produced a setup that worked, but
> > 
> > $ cp /home/auser/.Xauthority /root/.Xauthority
> > 
> > produced one that didn't. That seems strange enough to me.
> 
> Well, the copied cookie would only work for as long as the current X
> session remains running.  As soon as a new cookie is created for a
> new session, the copy becomes stale.

Yes, that makes sense. Missing context, of sorts. "Copying the X
auth file"  meant to me "copying freshly after each new X session".
By this I was adding implicitly some context which didn't necessarily
match reality.

Thanks, Greg :)

Cheers
 - t


signature.asc
Description: Digital signature

Re: 'apt upgrade' doet iets anders dan 'apt-get upgrade'

[Cecil Westerhof]

Richard Lucassen  writes:

> Ik weet niet hoeveel ruimte je hebt, maar als je ruimte hebt om een
> handmatige update te draaien dan zou het geen belemmering moeten zijn om
> cron-apt de packages te laten downloaden, dat is even groot namelijk. En
> draai na een update weer "apt autoclean" en eventueel "apt --purge
> autoremove"

Dat is het probleem niet, het probleem is dat het blijft staan. Laatst
kon ik door autoremove (als ik het goed heb) meerdere GB's vrijmaken.

-- 
Cecil Westerhof
Senior Software Engineer
LinkedIn: http://www.linkedin.com/in/cecilwesterhof

Re: [SOLUTION] Re: Bullseye: setting and using $DISPLAY after su -

[Greg Wooledge]

On Mon, Jan 04, 2021 at 07:48:03AM -0500, The Wanderer wrote:
> I parsed the preceding conversation as indicating that
> 
> $ ln -sf /home/auser/.Xauthority /root/.Xauthority
> 
> produced a setup that worked, but
> 
> $ cp /home/auser/.Xauthority /root/.Xauthority
> 
> produced one that didn't. That seems strange enough to me.

Well, the copied cookie would only work for as long as the current X
session remains running.  As soon as a new cookie is created for a
new session, the copy becomes stale.

Re: recommendations for supported, affordable hardware raid controller.

[Michael Stone]

On Mon, Jan 04, 2021 at 09:30:08AM +0200, Andrei POPESCU wrote:

On Du, 03 ian 21, 19:53:07, Michael Stone wrote:

Applications which need more data integrity
guarantees generally implement some sort of journalling and/or use atomic
filesystem operations. (E.g., write a temporary file, flush/sync,
rename--that guarantees either the old file or the new file will be present,
but not a partially written file.)


Unless I'm mistaken, this is somewhat similar to how copy-on-write works
for every write, except that the copy-on-write is done at block level
and with the added benefits that unchanged blocks are kept as they are
(less writes) and may even be shared between files (using less space).


COW is a different, somewhat related, thing. In itself it isn't 
sufficient for an application to be assured about the on-disk state at a 
particular time without using additional filesystem operations beyond a 
simple write(). In practice, those operations are a subset of what's 
necessary for other filesystems and most applications concerned about 
data integrity are going to implement the full set. (Few people want 
filesystem-specific applications.)

Re: Open Source Flash Alternatives

[Curt]

On 2021-01-04, didier gaumet  wrote:
> A little bit out-of-subject because it also mentions proprietary
> software, but there is a very recent article precisely on this
> subject:
> https://www.fastcompany.com/90590201/how-to-use-flash-to-play-old-games-after-adobe-discontinues-it
>
> (and being not intersted in games, I did not know archive.org gives
> access to old flash games) 

I was reading that gnash-dump (or dump-gnash?) can convert a swf to raw
format, which is then amenable to manipulation by ffmpeg.

Re: 'apt upgrade' doet iets anders dan 'apt-get upgrade'

[Richard Lucassen]

On Mon, 04 Jan 2021 01:54:23 +0100
Cecil Westerhof  wrote:

> > Draai je wel eens "apt clean"?
> 
> Nope, daar liep ik dus laatst tegenaan.

En wellicht een idee om de deb-src uit de sources.list te halen als die
er nog in staan. Scheelt ook weer MB's. 

> > Maar ik gebruik het "niet downloaden" dus nooit, maar volgens mij
> > kun je dat gewoon uitzetten, je krijgt dan alleen de notificatie:
> >
> > $ cat /etc/cron-apt/action.d/3-download 
> > autoclean -y
> > dist-upgrade -d -y -o APT::Get::Show-Upgraded=true
> >
> > Volgens mij kun je het daarmee instellen. Met dat apt is alles
> > mogelijk, je moet alleen een universitaire studie ervoor volgen :)
> 
> Ik heb nooit een universitaire studie gevolgd. ;-)
> Voorlopig werkt het, maar ik zou binnenkort eens in het bovenstaande
> kunnen duiken.

Ik weet niet hoeveel ruimte je hebt, maar als je ruimte hebt om een
handmatige update te draaien dan zou het geen belemmering moeten zijn om
cron-apt de packages te laten downloaden, dat is even groot namelijk. En
draai na een update weer "apt autoclean" en eventueel "apt --purge
autoremove"

-- 
richard lucassen
http://contact.xaq.nl/

Re: [SOLUTION] Re: Bullseye: setting and using $DISPLAY after su -

[The Wanderer]

On 2021-01-04 at 07:32, Greg Wooledge wrote:

> On Fri, Jan 01, 2021 at 07:52:40PM +0100, to...@tuxteam.de wrote:
> 
>> On Fri, Jan 01, 2021 at 10:24:44AM -0700, Charles Curley wrote:

>>> Bingo! That, rather than copying .Xauthority, gave me a fix.
>> 
>> Huh? That is strange. I mean: great it worked for you, but I'd like
>> to learn what is going on there :-)
> 
> What don't you understand?  In order for an X client to run, it
> needs two pieces of information: the DISPLAY to talk to, and the
> authorization to be allowed to talk.

I parsed the preceding conversation as indicating that

$ ln -sf /home/auser/.Xauthority /root/.Xauthority

produced a setup that worked, but

$ cp /home/auser/.Xauthority /root/.Xauthority

produced one that didn't. That seems strange enough to me.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: [SOLUTION] Re: Bullseye: setting and using $DISPLAY after su -

[Greg Wooledge]

On Fri, Jan 01, 2021 at 07:52:40PM +0100, to...@tuxteam.de wrote:
> On Fri, Jan 01, 2021 at 10:24:44AM -0700, Charles Curley wrote:
> > On Thu, 31 Dec 2020 22:30:34 -0600
> > David Wright  wrote:
> > 
> > >   $ /bin/su -
> > >   Password:
> > >   ahost ~# xeyes -display :0.0
> > >   Xlib: connection to ":0.0" refused by server
> > >   Xlib: Client is not authorized to connect to Server
> > >   Error: Can't open display: :0.0
> > >   ahost ~# ln -s ~auser/.Xauthority .Xauthority
> > 
> > Bingo! That, rather than copying .Xauthority, gave me a fix.
> 
> Huh? That is strange. I mean: great it worked for you, but I'd
> like to learn what is going on there :-)

What don't you understand?  In order for an X client to run, it needs
two pieces of information: the DISPLAY to talk to, and the authorization
to be allowed to talk.

For the authorization piece, the client looks for an MIT-magic-cookie
in a file named by the XAUTHORITY variable, or if that variable isn't
set, then it looks for the file $HOME/.Xauthority .

By creating this symlink, David has forever tied root's ~/.Xauthority
file to the one in auser's home directory.  Whenever an X client running
as root tries to run, in the absence of the XAUTHORITY variable, it will
look at ~root/.Xauthority which is a symlink to ~auser/.Xauthority which
is presumably on a local file system that root can read.  So the client
can read the MIT-magic-cookie, so it can authenticate itself to the X
server, so it can run.

This will fall on its face if some user other than auser happens to be
the one who started the X session.

Re: Bullseye: setting and using $DISPLAY after su -

[Greg Wooledge]

On Thu, Dec 31, 2020 at 05:49:02PM -0700, Charles Curley wrote:
> On Thu, 31 Dec 2020 17:15:40 -0500
> Greg Wooledge  wrote:

> Also, if I want to run as root, I want access to all the rootty system
> administrator things like fdisk and fsck. Plain vanilla su leaves one
> with the unprivileged user's PATH.

Only since buster, and this is fixable.  Just create this file with this
content:

unicorn:~$ cat /etc/default/su
ALWAYS_SET_PATH yes


> > It's worth pointing out that even on buster, "su -" does in fact clear
> > the value of DISPLAY,

> Also on buster:

> charles@hawk:~$ su -
> Password: 
> 
> Today is Setting Orange, the 73rd of The Aftermath, 3186. All Hail Discordia! 
> root@hawk:~# env | grep DISPLAY
> DISPLAY=:0

Clearly you're doing something special in root's .profile -- at the
very least, you're running that ddate command.  Is it possible you're
also hard-coding something like 'export DISPLAY=:0' there?

> root@hawk:~# xclock &
> [1] 3550
> root@hawk:~# 
> 
> (xclock ran successfully.)

Is it possible you also hard-coded something like
'export XAUTHORITY=/home/charles/.Xauthority' in root's .profile?

Re: Intermittent problem with integrated webcam / Thinkpad E130/ Stretch

[Georgi Naplatanov]

On 1/4/21 1:00 PM, Ottavio Caruso wrote:
> Hi,
> 
> $ uname -a
> Linux e130 4.9.0-14-amd64 #1 SMP Debian 4.9.246-2 (2020-12-17) x86_64
> GNU/Linux
> 
> $ cat /etc/debian_version
> 9.13
> 
> $ inxi -M
> Machine:
>   Type: Laptop System: LENOVO product: 33588QG v: ThinkPad Edge E130
> 
> I have had a problem with having the integrated webcam to be recognized
> by various applications (cheese, Microsoft Teams [yes...], Zoom, etc).
> It does work sometimes and it doesn't at other times.
> 
> I have various kernels installed (4.9.0-11-amd64 all the way through
> 4.9.0-14-amd64) and rebooting into each of these kernels won't make much
> difference.
> 
> I have uninstalled, purged and reinstalled build-essential
> linux-headers-`uname -r` linux-image-amd64`uname -r` (for each of the
> kernel versions) and usbutils, and I have also uninstalled tlp, but it
> doesn't seems to make much difference.
> 
> This is the full log of `dmesg|grep video` of today, when I had the last
> failure:
> 
> https://paste.debian.net/plainh/1c22d1aa
> 
> I can't upgrade to Debian stable for a number of reasons that it will
> take to long to explain and I have to stick with Stretch for the time
> being. I've only had this problem for the last 6 months, presumably
> after some upgrades.
> 
> Any help will be appreciated.
> 
> 


Hi Ottavio,

if the issue with your camera is a kernel thing then you can install
newer kernel from backports.

According to this page -

https://tracker.debian.org/pkg/linux

Linux  4.19.118 is available for Debian 9.

HTH

Kind regards
Georgi

Re: Open Source Flash Alternatives

[didier gaumet]

A little bit out-of-subject because it also mentions proprietary software, but 
there is a very recent article precisely on this subject:
 
https://www.fastcompany.com/90590201/how-to-use-flash-to-play-old-games-after-adobe-discontinues-it

(and being not intersted in games, I did not know archive.org gives access to 
old flash games) 

Re: [Résolu]: openvpn --route-up et --route-pre-down

[Daniel Caillibaud]

Le 02/01/21 à 01:07, Jean-Marc  a écrit :
> Bon, si j'ajoute un shebang #!/bin/bash, openvpn ne me donne plus de
> message d'erreur mais mon script ne fait rien.

C'est bizarre, /bin/bash existe et est exécutable ?

-- 
Daniel

Je m’intéresse à l’avenir car c’est là que j’ai décidé de passer le restant de 
mes jours.
Woody Allen