Re: Bookworm: missing sbin in root path?

[Carl Fink]

Yes, I did use su. I had no idea that would cause a problem.

Thanks for the pointer. I created /etc/default/su, which should
resolve this.

 -Carl Fink

On 7/1/23 21:38, Greg Wooledge wrote:

On Sat, Jul 01, 2023 at 08:58:44PM -0400, Carl Fink wrote:

When I type "/usr/sbin/adduser", that works, but shouldn't root default to
having sbin in its path?

You probably used su.

 describes the change
and the known fixes.

Re: Out of Range Monitor Problim

[Felix Miata]

Stephen P. Molnar composed on 2023-07-01 13:44 (UTC-0400):

> OK. Now I boot into as user, but the resolution leaves something to be 
> desired, 1024x760.

> The new card is a ViasiontekHD5450 16GB D3 DVH PCI Card.
 
> The Monitor is a LG Flattop 24EN33TW-B with a recommended resolution of 
> 1920X1080 67500 kHz 60kHz +/+ (Which, I think the resolution was before 
> the mishap)
 
> I installed inxi and get the following results:
 
> (base) comp@AbNormal:~$ inxi -GSaz
> System:    Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
>     parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64
>     root=UUID=9848531c-e052-44b0-a5b6-9ea786f9eaee ro quiet
>     Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: 
> xfwm4 dm: LightDM 1.26.0
>     Distro: Debian GNU/Linux 11 (bullseye)
> Graphics:  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] 
> vendor: VISIONTEK
>     driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68f9 
> class ID: 0300
>     Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon
>     unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1
>     Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm 
> (10.7x8.0")
>     s-diag: 339mm (13.3")
>     Monitor-1: VGA-0 res: 1024x768 hz: 60
>     OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-23-amd64 
> LLVM 11.0.1)
>     v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes
 
> While I am quite comfortable, doing molecular orbital computations, I 
> would be very uncomfortable trying to proceed further.

Now that you have a GPU with outputs other than VGA, find a DVI-to-HDMI or
HDMI-to-HDMI cable and connect that HD5450 to your LG instead of the VGA
cable. If that isn't any better, connect it to a TV's HDMI input to see what
results. I suspect your VGA connection is the root problem, either the cable,
or the VGA connector on your LG. All is good here with Bullseye and HD5450
using VGA connection, HDMI connection, and/or DVI connection:

# inxi -GSaz
System:
  Kernel: 5.10.0-23-amd64 arch: x86_64 bits: 64 compiler: gcc v: 10.2.1
parameters: ro root=/dev/sda12 noresume net.ifnames=0 ipv6.disable=1
consoleblank=0 preempt=full mitigations=off
  Desktop: Trinity v: R14.1.0 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0
vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 11 (bullseye)
Graphics:
  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] vendor: XFX Pine
driver: radeon v: kernel arch: TeraScale-2 code: Evergreen
process: TSMC 32-40nm built: 2009-15 pcie: gen: 2 speed: 5 GT/s lanes: 16
ports: active: DVI-I-1,VGA-1 empty: HDMI-A-1 bus-ID: 01:00.0
chip-ID: 1002:68f9 class-ID: 0300 temp: 60.0 C
  Display: x11 server: X.Org v: 1.20.11 driver: X: loaded: modesetting
alternate: fbdev,vesa dri: r600 gpu: radeon display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00")
s-diag: 803mm (31.62")
  Monitor-1: DVI-I-1 pos: right model: Dell P2213 serial: 
built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
  Monitor-2: VGA-1 pos: primary,left model: NEC EA243WM serial: 
built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
  API: OpenGL v: 3.3 Mesa 20.3.5 renderer: AMD CEDAR (DRM 2.50.0 /
5.10.0-23-amd64 LLVM 11.0.1) compat-v: 3.1 direct-render: Yes
# hwinfo --monitor
23: None 00.0: 1 Monitor
  [Created at monitor.125]
  Unique ID: rdCR.VxQp9HL+fzB
  Parent ID: VCu0.SWTcMEVMYM4
  Hardware Class: monitor
  Model: "NEC EA243WM"
  Vendor: NEC "NEC"
  Device: eisa 0x6863 "EA243WM"
  Serial ID: "1Z101367NA"
  Resolution: 640x480@60Hz
  Resolution: 800x600@56Hz
  Resolution: 800x600@60Hz
  Resolution: 1024x768@60Hz
  Resolution: 1280x960@60Hz
  Resolution: 1280x1024@60Hz
  Resolution: 1280x720@60Hz
  Resolution: 1920x1200@60Hz
  Size: 519x324 mm
  Year of Manufacture: 2011
  Week of Manufacture: 48
  Detailed Timings #0:
 Resolution: 1920x1200
 Horizontal: 1920 1968 2000 2080 (+48 +80 +160) -hsync
   Vertical: 1200 1203 1209 1235 (+3 +9 +35) +vsync
Frequencies: 154.00 MHz, 74.04 kHz, 59.95 Hz
  Driver Info #0:
Max. Resolution: 1920x1200
Vert. Sync Range: 56-61 Hz
Hor. Sync Range: 31-77 kHz
Bandwidth: 154 MHz
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #10 (VGA compatible controller)
...
# hwinfo --gfxcard
16: PCI 100.0: 0300 VGA compatible controller (VGA)
  [Created at pci.386]
  Unique ID: VCu0.SWTcMEVMYM4
  Parent ID: vSkL.l4tEjTIzexA
  SysFS ID: /devices/pci:00/:00:01.0/:01:00.0
  SysFS BusID: :01:00.0
  Hardware Class: graphics card
  Model: "ATI Cedar [Radeon HD 5000/6000/7350/8350 Series]"
  Vendor: pci 0x1002 "ATI Technologies 

Re: RFS: binutils-msp430/2.40.50~ti1 [ITA] -- Binary utilities supporting TI's MSP430 targets

[Leandro Cunha]

Oi Charles,

On Sat, Jul 1, 2023 at 10:46 PM Carlos Henrique Lima Melara
 wrote:
>
> Boa noite, Thiago.
>
> Eu não sou um DD, então não posso fazer o sponsor, mas dei uma olhadinha
> rápida no empacotamento e posso dar umas dicas.
>

Eu mostrei pro Samuel este e-mail.
Enquanto isso, ele pode fazer os ajustes recomendados por você.

-- 
Cheers,
Leandro Cunha
-BEGIN PGP PUBLIC KEY BLOCK-

mQINBF/gQ8gBEADHVKgoWsUWNGVvR6sMhBPUdBUEH+QALpr1QYXhetBfRwaY0HWN
pKgejHdxKO8H+kIhRMoh89CCKg3hAJ9LmOOTXkX7U5/Cya/zRMKk5zBD3rKIaugh
0XYT15Nz1jwL7TIDG25yPSloDtVgVXTep0ZzKsNYJjb4OAqa88cvUEJEhhqrldlR
gpNbkixEh5ituO8pMShEBWqLs3yt4Hr1VFWnTIm4dl/JLBHpexzubDOw/mKCTpNd
A1JGHTvce1wtJ2fMzCVzhEjd5pyjLZV/o8hVw2/ON/yXvpJuz0lV/hiW0M+cDcas
sKftErtsZpRy3wwXdkBcJt6soYuqfCHwgMfL2iC6mPviE8xWAHMOmhdC3wDskZpb
RcLfH5IMYajJAGRO/GCMcKKbq7WkEOeloivtg64xBlYuJf9aOcHKP/8R3EObiNp7
ubQAJtV3pEGD4mx1mhutFxDHB+CfnxE3dWvxZSV9y1n4UOzkDJ3kDx5Ee0MbRvJD
w6aXKc6dhYREgh7hLDcMFz+3LcBiZDLxI3g+SHe3Bl61vdsnPno+0HhCzvB+fL4S
eoy7Myfiunz9BrB2HPN+wNCT0YgV+Kv8QoDGzBwos5H1vUJSY4t59w6xoXAYUsAm
hjAM8s+rUtG40mcUWePd8kZtgE9IV1eQ+Qt8/SNpSdRnUunmIGl3JjHvEwARAQAB
tClMZWFuZHJvIEN1bmhhIDxsZWFuZHJvY3VuaGEwMTZAZ21haWwuY29tPokCTgQT
AQoAOBYhBLT5oBCvKN3HzFEPK8LZ4zKUW9A8BQJf4EPIAhsDBQsJCAcCBhUKCQgL
AgQWAgMBAh4BAheAAAoJEMLZ4zKUW9A8FjAQAKWYqiLpLUD+DLB+NSy3DI3rf9z3
k0vE7TLaEjdEM5CQWN+j4vBqMnAckdcARvSWPndTjp8K+mtFF4PyfhNbS64z/a7L
F3DdhmX73n7LKFG8Ow9NZwcrkmPwH5WcP7mXTh6R+6/+OSL/K85NB8MLlxQTJOni
julVax9JEZjwBaP2HLCu53Zq9gZcvJlXoAoTHyTxKdp8Mh8V+Qit26E78o9c6SQD
Dq9eyMRG8hYCRfreDjKceRkYHjECySlk+VoI1ssVs07Dqvxg6qSyP4RnW+1+W74C
s0yIyuC/eRJpMAf1PBQEOOrVcTfRfpN+go955t21yIAvT58vqotTM5eaqXYIQn/y
sC4lThZai/ZBZHxl5Mbv42WkkYdjisLQOCALIMBpj5nq4oh2C+kvMupcuBKfERgV
dguU51MzfQktKb6d5y777zYnDaFMQDD2IfiD/C7ln5A9LP/L54ixlA3uRmWx/yAx
/m+Zusws98j4Eq/jw5T54XW655m6lMCTE9WXLJkgxrRcEonHSllbgRSsToEmWq0Z
doxcnpagHdcGQzW+cu2VOGi1da73ZFmrn+ptJgc8cW2suO06IeArOi0TzIg7e65j
Xp2DbJCpFrfzEuBb1u71WvB8V2MkAfJZx/uZJPCA936B4HT8YGPEMzlQRIHI2Y9C
+DloyzlBLTS1EMKuuQINBF/gQ8gBEAC47o9u1Wm9jZ6RC+lfxEDEvVS7MmI5VzSy
q04rFttWwbKix13pc65aDlk47LxWrb84N3Gnf1E/OTsLTXqC7u5JZ7YJkC6CsPbo
D1sQkfCiJCFCTgf7dydEVt8ujS/Uu1kz86ufdRwaMRcvBZAORGdB58LEsLB65WN4
hLRYF7xvcxu6t7FGrIYereaxUAWLA2B/ZnCEdOY94w7s0uaPjHdf4lfHebuZ7T08
iG5ACDvKBjgaFArGfdNYWchXJgbOEg14bGj40/8LuBKQMZASiFSqLPZxoporK9FY
xBw+D080dUWWD5g868TZ3pkM3DXO9bdq22IBKqKOep8CnuKgoDpUvA8dTEY/UDCn
sdOlBUK/Y9zTGVmD/90cO/xkvkV78suqiBnwBSddPzVS0EuiWwrLGu8gaY4EyM/X
7khlbTcMgh4njzUCAE6Tq+TbXSxn86wuOybVY5Y+I99LNdsocI5SIn2nDh2IOi00
4dE/iwO2MatWIOLFBC7pw8Xv4UHZY+WIf3Y/6XjExpllhUkeB6BwZpTr1SXk+cug
q5Dj5i4aGn2LrvQJ57terqUWYyDUBFgXTc4SPOzT5og8CavBgHfrQoFwSnRZ2oyX
xtZhEDI5Pk2j1qTbOhXZ29po4rPNWHMq2HQgM0I+BqQndsoVdkPOFzS2wKkdXjCz
bNYcyanusQARAQABiQI2BBgBCgAgFiEEtPmgEK8o3cfMUQ8rwtnjMpRb0DwFAl/g
Q8gCGwwACgkQwtnjMpRb0Dzh6g//ZjXaWSzKmG5ZS6XJa/ZOokkE2hFOFusWX8Qa
hEwLAnTFEy02dLfV54rKwmu2jHPDKLhE+iYtusvytueZAzVRyQahv0RE4BH8Emqw
gQdBwyJ/L+QhUp/lMdJ6Hh/2ZSZmzU29U24vnY+U+haoB1fLnA3lXgOP59kMLGud
lERR2Vluuc7TcpzvcaRWgrQRU2vSrrBBEp6y07iVKbRM/9yhE/aHJahLbhKh2Dk9
WJvHPnhYJY5yU+Y5vTl3BiW5+EuzMBdPUawOWKhqCq9dswn0GL1g/vlt/bdU/6DO
jECQ6fssTAtDjRClXySsS3X0mh8y8qlGvMPB4anfvOy4+4nUV6IESdJftKn2SMGd
CA3MaQ+S7frWn5v7GIWSC9vumCsiu1JTOugLmbVmu5m5nFsyllavm/k9LtOtswuF
fHM/SlXLFuGBWU6XceqaM2dpP8i5jGz0vIGMhqoFNgXWGO1NhwR1rmeU1CMpnM5e
Wue4h/+mJiuEzuZcmzOcwq3HGMUXO0jZDgLEmlnenO9czhrLuGZaMXGdwnIk0G3O
+SqH36v7blnDh96RXpgaa+ifTHd0qKeoVXVwSq/9jNtHSQrI+NJcTpMhu73xtxhX
UFPr/31+IFLWepC5GDwdu/gQm5E6ntGyxE2p2v76pcjz7SGdXjPFZjqekBveEJuW
fNdY6Ns=
=rdCA
-END PGP PUBLIC KEY BLOCK-

Re: Bookworm: missing sbin in root path?

[Greg Wooledge]

On Sat, Jul 01, 2023 at 08:58:44PM -0400, Carl Fink wrote:
> When I type "/usr/sbin/adduser", that works, but shouldn't root default to
> having sbin in its path?

You probably used su.

 describes the change
and the known fixes.

Bookworm: missing sbin in root path?

[Carl Fink]

Hi,

So I just installed Debian Bookworm on a new system. And things aren't 
there. I noticed that "adduser is already the newest version (3.134)." 
(according to Apt) but typing "adduser" at a terminal prompt does ... 
nothing. Not found.


So, I installed locate (also not present by default?) and discovered 
that although the package installed /usr/sbin/adduser, somehow root 
doesn't have /user/sbin in its PATH.


When I type "/usr/sbin/adduser", that works, but shouldn't root default 
to having sbin in its path?


-Carl Fink

Change Cursor Theme For Debian 12

[Ahmad Ismail]

I am using:

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
...

My GDM version is:

$ gdm3 --version
GDM 43.0

I have disabled wayland and am using xorg.

Details Of Debian User:

$ cat /etc/passwd | rg gdm
Debian-gdm:x:112:121:Gnome Display Manager:/var/lib/gdm3:/bin/false

The icon is located in /usr/share/icons/Bibata-Modern-Ice.

Following ArchWiki, I have run the following commands:

xhost +SI:localuser:Debian-gdm
/usr/bin/sudo -u Debian-gdm dbus-launch gsettings set
org.gnome.desktop.interface cursor-theme 'Bibata-Modern-Ice'

It did not change the theme.

Again, I have also tried /etc/gdm3/greeter.dconf-defaults.

[org/gnome/desktop/interface]
cursor-theme='Bibata-Modern-Ice'
cursor-size=32
text-scaling-factor=1.25
gtk-theme='Solarized-DarkArc-Cyan'
icon-theme='Solarized-Dark-Cyan-Numix'

Then ran `sudo dconf update`.

Still The cursor theme is not CHANGED (though it changed the cursor size).

What can I do?

Change Cursor Theme For Debian 12

[Ahmad Ismail]

I am using:

$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/;
SUPPORT_URL="https://www.debian.org/support;
BUG_REPORT_URL="https://bugs.debian.org/;

My GDM version is:

$ gdm3 --version
GDM 43.0

I have disabled wayland and using xorg.

Details Of Debian User:

$ cat /etc/passwd | rg gdm
Debian-gdm:x:112:121:Gnome Display Manager:/var/lib/gdm3:/bin/false

The icon is located in /usr/share/icons/Bibata-Modern-Ice.

Following ArchWiki, I have run the following commands:

xhost +SI:localuser:Debian-gdm
/usr/bin/sudo -u Debian-gdm dbus-launch gsettings set
org.gnome.desktop.interface cursor-theme 'Bibata-Modern-Ice'

It did not change the theme.

Again, I have also tried /etc/gdm3/greeter.dconf-defaults.

[org/gnome/desktop/interface]
cursor-theme='Bibata-Modern-Ice'
cursor-size=32
text-scaling-factor=1.25
gtk-theme='Solarized-DarkArc-Cyan'
icon-theme='Solarized-Dark-Cyan-Numix'

Then ran sudo dconf update.

Still The cursor theme is not changing (though it changed the cursor size).

What can I do?

Re: Transport endpoint is not connected

[hlyg]

Thank David, 3 devices are plugged to usb hub: wifi adapter, receiver 
for wireless keyboard/mouse and usb lamp for power only.


i don't have energy to troubleshoot it as it's ok with buster and 
bullseye,  problem is with deb12, not with my usb device


it's not too bad that newly stable deb12 isn't ready for me as deb10/11 
meet my needs

Re: Out of Range Monitor Problim

[David Christensen]

On 7/1/23 10:44, Stephen P. Molnar wrote:
OK. Now I boot into as user, but the resolution leaves something to be 
desired, 1024x760.


The new card is a ViasiontekHD5450 16GB D3 DVH PCI Card.

The Monitor is a LG Flattop 24EN33TW-B with a recommended resolution of 
1920X1080 67500 kHz 60kHz +/+ (Which, I think the resolution was before 
the mishap)


I installed inxi and get the following results:

(base) comp@AbNormal:~$ inxi -GSaz
System:    Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64
    root=UUID=9848531c-e052-44b0-a5b6-9ea786f9eaee ro quiet
    Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: 
xfwm4 dm: LightDM 1.26.0

    Distro: Debian GNU/Linux 11 (bullseye)
Graphics:  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] 
vendor: VISIONTEK
    driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68f9 
class ID: 0300

    Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon
    unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1
    Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm 
(10.7x8.0")

    s-diag: 339mm (13.3")
    Monitor-1: VGA-0 res: 1024x768 hz: 60
    OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-23-amd64 
LLVM 11.0.1)

    v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes

While I am quite comfortable, doing molecular orbital computations, I 
would be very uncomfortable trying to proceed further.


Guidance would be very much appreciated.

Thanks in advance.


On 6/29/23 15:18, David Christensen wrote:
> Do you have a second machine that can log into the subject machine via
> ssh(1)?


David

Re: Configuration asterisk

[didier gaumet]

Le 01/07/2023 à 12:02, BERTRAND Joël a écrit :
[...]

retourne :
[Jul  1 12:00:13] WARNING[12569][C-0001] chan_sip.c: Purely numeric
hostname (0x), and not a peer--rejecting!
[Jul  1 12:00:13] NOTICE[12569][C-0001] app_dial.c: Unable to create
channel of type 'SIP' (cause 20 - Subscriber absent)


Bonjour,

Avertissement habituel: Asterisk, je ne connais que de nom, je ne l'ai 
jamais configuré, installé ou utilisé. SIP, j'ai eu un compte gratuit 
dans un lointain passé pour essayer via je ne sais plus trop quel outil 
de téléphonie GUI Linux.


- le "warning" ci-dessus m'incite à penser que tu utilises l'ancien 
pilote SIP d'Asterisk (chan_sip), qui d'après le wiki Asterisk est 
déprécié de puis Asterisk 17 et est carrément enlevé à partie d'Asterisk 
21. Il vaudrait donc a priori mieux utiliser le nouveau pilote 
(chan_pjsip), y a de la doc à ce sujet:

https://wiki.asterisk.org/wiki/display/AST/Configuring+chan_sip
j'ai jeté un oeil au wiki Debian Asterisk, il en est encore à l'ancien 
pilote

par contre tu peux jeter un oeil à l'artcile Asterisk du wiki Archlinux:
https://wiki.archlinux.org/title/asterisk#PJSIP

- la "notice" ci-dessus semble indiquer que ton compte d'abonné auprès 
d'un fournisseur de service SIP n'est pas trouvé par Asterisk (j'ai pas 
creusé pour savoir pourquoi, ni comment corriger si c'est le cas)

Re: Out of Range Monitor Problim

[Stephen P. Molnar]

OK. Now I boot into as user, but the resolution leaves something to be 
desired, 1024x760.


The new card is a ViasiontekHD5450 16GB D3 DVH PCI Card.

The Monitor is a LG Flattop 24EN33TW-B with a recommended resolution of 
1920X1080 67500 kHz 60kHz +/+ (Which, I think the resolution was before 
the mishap)


I installed inxi and get the following results:

(base) comp@AbNormal:~$ inxi -GSaz
System:    Kernel: 5.10.0-23-amd64 x86_64 bits: 64 compiler: gcc v: 10.2.1
   parameters: BOOT_IMAGE=/boot/vmlinuz-5.10.0-23-amd64
   root=UUID=9848531c-e052-44b0-a5b6-9ea786f9eaee ro quiet
   Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 info: xfce4-panel wm: 
xfwm4 dm: LightDM 1.26.0

   Distro: Debian GNU/Linux 11 (bullseye)
Graphics:  Device-1: AMD Cedar [Radeon HD 5000/6000/7350/8350 Series] 
vendor: VISIONTEK
   driver: radeon v: kernel bus ID: 01:00.0 chip ID: 1002:68f9 
class ID: 0300

   Display: x11 server: X.Org 1.20.11 driver: loaded: ati,radeon
   unloaded: fbdev,modesetting,vesa display ID: :0.0 screens: 1
   Screen-1: 0 s-res: 1024x768 s-dpi: 96 s-size: 271x203mm 
(10.7x8.0")

   s-diag: 339mm (13.3")
   Monitor-1: VGA-0 res: 1024x768 hz: 60
   OpenGL: renderer: AMD CEDAR (DRM 2.50.0 / 5.10.0-23-amd64 
LLVM 11.0.1)

   v: 3.3 Mesa 20.3.5 compat-v: 3.1 direct render: Yes

While I am quite comfortable, doing molecular orbital computations, I 
would be very uncomfortable trying to proceed further.


Guidance would be very much appreciated.

Thanks in advance.


On 06/30/2023 02:32 PM, Stephen P. Molnar wrote:
The problem is solved. Apparently the PCI card had a loose connector, 
so I replaced it.


As] soon as  adjust the resolution it'll be back to normal.

Many thanks to all that answered by request for help.

On 6/29/2023 4:09 PM, Felix Miata wrote:

Stephen P. Molnar composed on 2023-06-29 15:15 (UTC-0400):


All components were purchased from tho Microcenter herein Columbus.
It could, in fact, connect to a TV on the LAN in the same room, But now
I get form the TV: Computer No signal is it on?
Not a good sign. :( Did you turn the TV on, and to the correct input, 
before
turning on the PC? Some TVs don't like being late to the boot. So do 
some GPUs.



inxi -GSaz, in safe mode, returns- bash: inxi: command not found
If network is working, sudo apt install inxi will install it, but 
because

Bullseye's inxi is a broken antique, better to do the following as root:

cd /usr/local/bin && wget -O inxi smxi.org/inxi && chmod +x inxi
from:
https://smxi.org/docs/inxi-installation.htm#inxi-manual-install

to get the much improved current version. Inxi -Gaz is the best there 
is for

providing basic graphics troubleshooting info.


cat for both logs returns:  no such file or directory
Bad sign. I never use Wayland, so can't be sure what if any logging 
it does that
ordinary people can locate. Xorg should have left an old one in 
either location if
there is no current one. I think Wayland leaves its stuff in the 
journal:




Let me pose a hypothetical - Would installing Debian 12 on a different
drive boot. or would I (most likely) muck-up the entire computer?
It's possible to muck up what you have, but if you remove the current 
drive and
install the different one and Bookworm, it might be your best way 
forward. If the
installer can't work either, it would be near certain you've acquired 
a hardware
problem, hopefully easily resolved with a graphics card swap if you 
can locate one
to try without too much trouble. What to look for might depend on 
what you have in
there now. NVidia as good at giving people headaches like you have. 
Intel only
just began (after more than two decades of not) providing discrete 
graphics cards.
So hopefully you could get hands on a PCIe AMD card made less than 10 
years ago to

try.

Simply starting the Bookworm installer, if it starts at all, might 
say a lot.




--
Stephen P. Molnar, Ph.D.
https://insilicochemistry.net
(614)312-7528 (c)
Skype:  smolnar1

Re: Why does Debian have code names for releases?

[Joe]

On Sat, 01 Jul 2023 10:45:54 -0400
Stefan Monnier  wrote:

> > But I can't see what's wrong with codenames. It's not just a
> > "tradition", it's standard practice in most fields of endeavour.
> > You slap a name on a project, and everyone knows what they're
> > talking about. Unlike numbers, names are memorable and unambiguous
> > (when well-chosen).  
> 
> AFAICT codenames are common before a project is released.  They're
> much less common afterwards.
> 
> > You don't have to memorize all of Debian's codenames in order, do
> > you?  
> 
> I regularly have to figure out which of Buster/Bookworm/Bullseye/...
> is stable/testing/oldstable, and I must admit that I tend to forget
> and end up having to look it up.
> 
> 
>
Three Bs in a row didn't help.

-- 
Joe

Re: cannot install odcb mariadb in bookworm

[John Covici]

OK, thanks very much.

On Sat, 01 Jul 2023 10:48:10 -0400,
Alexander V. Makartsev wrote:
> 
> [1  ]
> On 01.07.2023 18:44, John Covici wrote:
> > OK, thanks much --what do I add to my sources list for the proposed
> > updates?  Do I need all the lines ending with main free etc. or just
> > one line?
> > 
> It is up to you. If you need to solve the "odbc mariadb" problem,
> I think selecting just "main" will be enough, eg.:
> deb https://deb.debian.org/debian/ bookworm-proposed-updates main
> deb-src https://deb.debian.org/debian/ bookworm-proposed-updates main
> 
> Or you can add all other sections like so:
> deb https://deb.debian.org/debian/ bookworm-proposed-updates main
> contrib non-free non-free-firmware
> deb-src https://deb.debian.org/debian/ bookworm-proposed-updates
> main contrib non-free non-free-firmware
> 
> Consult Debian wiki for additional info:
> https://wiki.debian.org/SourcesList
> 
> -- 
> With kindest regards, Alexander.
> 
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> ⠈⠳⣄
> [2  ]

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: Why does Debian have code names for releases?

[Roger Price]

On Sat, 1 Jul 2023, David Wright wrote:


Unlike numbers, names are memorable and unambiguous (when well-chosen).


This claim is far from evident and needs justification.  The only example I can 
think of is project number 401 which later became the product "Titanic". However 
the name is not memorable in itself: what we remember is the maritime disaster.


Roger

Re: Why does Debian have code names for releases?

[Dan Ritter]

David Wright wrote: 
> On Mon 26 Jun 2023 at 17:22:04 (-0400), Jeffrey Walton wrote:
> > On Mon, Jun 26, 2023 at 4:45 PM Dan Ritter  wrote:
> > > riveravaldez wrote:
> > > > It would be possible, as an alternative, to populate sources.list with 
> > > > '2021',
> > > > for instance, instead of 'bullseye', 'bookworm', etc.?
> > > >
> > > > We could have something like, 'Debian 2023 - Bookworm', so, preserving
> > > > tradition, but allowing '2023' to be used as an alternative replacement 
> > > > of
> > > > the traditional name maybe?
> > > >
> > > > Just an idea, looking for a simple solution...
> > > >
> > > > BTW, considering Debian doesn't have the marketing impositions of any
> > > > proprietary commercial product, I find 'Debian 2021', 'Debian 2023', 
> > > > etc.,
> > > > reasonably appealing...
> > >
> > > This would also be useful in my efforts to explain to my boss
> > > why we're upgrading the machines.
> > >
> > > "It's 2023 and we're running Debian 2021. It's time to upgrade."
> > 
> > ++
> 
> I don't see how that works. What would your codename be, instead of
> trixie? How do you know?

I wouldn't care, because "2023" would be a synonym for
"bookworm" in all the appropriate files.

> a project, and everyone knows what they're talking about. Unlike numbers,
> names are memorable and unambiguous (when well-chosen).

buster, bullseye, bookworm. So we can't depend on them to be
well-chosen.

> You don't have to memorize all of Debian's codenames in order, do you?
> There are about three or four in current use at any one time. (And the
> release numbers might be monotonic, but they're not sequential, so
> memorizing them would be just as tricky.)

Since I've been using Debian since ... 1.3 ? I have been exposed
to at least a dozen names.

It would always have been of more benefit to be able to say
"that went stable in 2002" or "next stable release will probably
be in 2025" rather than "3 Woody" and "13 Trixie". Keeping the
fun name is absolutely fine and indeed useful -- because
schedules slip and no software should be released before its
time.

It's just that, when Trixie becomes stable, it would be very
useful to be able to put "2025" or "2026" in all my
documentation and config files instead of "13 Trixie".

-dsr-

Re: cannot install odcb mariadb in bookworm

[Alexander V. Makartsev]

On 01.07.2023 18:44, John Covici wrote:

OK, thanks much --what do I add to my sources list for the proposed
updates?  Do I need all the lines ending with main free etc. or just
one line?

It is up to you. If you need to solve the "odbc mariadb" problem, I 
think selecting just "main" will be enough, eg.:

deb https://deb.debian.org/debian/ bookworm-proposed-updates main
deb-src https://deb.debian.org/debian/ bookworm-proposed-updates main

Or you can add all other sections like so:
deb https://deb.debian.org/debian/ bookworm-proposed-updates main 
contrib non-free non-free-firmware
deb-src https://deb.debian.org/debian/ bookworm-proposed-updates main 
contrib non-free non-free-firmware


Consult Debian wiki for additional info:
https://wiki.debian.org/SourcesList

--
With kindest regards, Alexander.

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

Re: Why does Debian have code names for releases?

[Stefan Monnier]

> But I can't see what's wrong with codenames. It's not just a "tradition",
> it's standard practice in most fields of endeavour. You slap a name on
> a project, and everyone knows what they're talking about. Unlike numbers,
> names are memorable and unambiguous (when well-chosen).

AFAICT codenames are common before a project is released.  They're much
less common afterwards.

> You don't have to memorize all of Debian's codenames in order, do you?

I regularly have to figure out which of Buster/Bookworm/Bullseye/... is
stable/testing/oldstable, and I must admit that I tend to forget and end
up having to look it up.


Stefan

Re: Why does Debian have code names for releases?

[David Wright]

On Mon 26 Jun 2023 at 17:22:04 (-0400), Jeffrey Walton wrote:
> On Mon, Jun 26, 2023 at 4:45 PM Dan Ritter  wrote:
> > riveravaldez wrote:
> > > It would be possible, as an alternative, to populate sources.list with 
> > > '2021',
> > > for instance, instead of 'bullseye', 'bookworm', etc.?
> > >
> > > We could have something like, 'Debian 2023 - Bookworm', so, preserving
> > > tradition, but allowing '2023' to be used as an alternative replacement of
> > > the traditional name maybe?
> > >
> > > Just an idea, looking for a simple solution...
> > >
> > > BTW, considering Debian doesn't have the marketing impositions of any
> > > proprietary commercial product, I find 'Debian 2021', 'Debian 2023', etc.,
> > > reasonably appealing...
> >
> > This would also be useful in my efforts to explain to my boss
> > why we're upgrading the machines.
> >
> > "It's 2023 and we're running Debian 2021. It's time to upgrade."
> 
> ++

I don't see how that works. What would your codename be, instead of
trixie? How do you know?

But I can't see what's wrong with codenames. It's not just a "tradition",
it's standard practice in most fields of endeavour. You slap a name on
a project, and everyone knows what they're talking about. Unlike numbers,
names are memorable and unambiguous (when well-chosen).

You don't have to memorize all of Debian's codenames in order, do you?
There are about three or four in current use at any one time. (And the
release numbers might be monotonic, but they're not sequential, so
memorizing them would be just as tricky.)

Cheers,
David.

Re: Transport endpoint is not connected

[David Wright]

On Fri 30 Jun 2023 at 13:06:49 (+0800), hlyg wrote:
> Thank David! i suppose it close wifi connection (say goodbye to hot
> spot of cell phone) as i shutdown, i don't have network FS

So I assume you use have a wifi dongle, connected to the hub, that
communicates with the tethered phone's hotspot.

> i don't have usb disk plugged to usb hub

So what's the hub for?

> bookworm for both i386 and amd64 seem uncomfortable with my usb hub.
> 
> last few lines below show errors
> 
> i am now using bullseye, bookworm isn't stable enough for me

Just because of this hub, or for other reasons? Sorry, but I only see
snippets of information, and no intentions/reasons.

> Jun 27 05:38:10 debian kernel: usb 1-2: new high-speed USB device
> number 2 using ehci-pci
> Jun 27 05:38:10 debian kernel: usb 1-2: New USB device found,
> idVendor=14cd, idProduct=8601, bcdDevice= 0.00
> Jun 27 05:38:10 debian kernel: usb 1-2: New USB device strings: Mfr=1,
> Product=3, SerialNumber=0
> Jun 27 05:38:10 debian kernel: usb 1-2: Product: USB 2.0 Hub
> Jun 27 05:38:10 debian kernel: usb 1-2: Manufacturer: USB Device
> Jun 27 05:38:10 debian kernel: hub 1-2:1.0: USB hub found
> Jun 27 05:38:10 debian kernel: hub 1-2:1.0: 4 ports detected
> Jun 27 05:38:10 debian kernel: usb 1-3: new high-speed USB device
> number 3 using ehci-pci
> Jun 27 05:38:10 debian kernel: usb 1-3: device descriptor read/64, error -71
> Jun 27 05:38:10 debian kernel: usb 1-3: device descriptor read/64, error -71
> Jun 27 05:38:10 debian kernel: usb 1-3: new high-speed USB device
> number 4 using ehci-pci
> Jun 27 05:38:10 debian kernel: usb 1-3: device descriptor read/64, error -71
> Jun 27 05:38:10 debian kernel: usb 1-3: device descriptor read/64, error -71
> Jun 27 05:38:10 debian kernel: usb usb1-port3: attempt power cycle

I don't have much experience of interpreting these numbers, but isn't
this error coming from the device plugged into the hub (1-3) rather
than the hub itself (1-2)?

Cheers,
David.

Re: Very small fonts on 4K monitor [solved]

[Stefan Monnier]

>> I think you'll want to read things like
>>  https://wiki.debian.org/MonitorDPI
> That's a rather old reference and not particularly relevant to Debian 12 /

Sorry, the information I mean to convey is that your problem is probably
an incorrect DPI info (presumably one influenced by the display driver
since changing the driver affects the result).

E.g. you may want to compare the physical screen size that `xrandr`
announces with the real size of your monitor (and also comparing the
size you get with nouveau and the one you get with nvidia).


Stefan

Re: cannot install odcb mariadb in bookworm

[John Covici]

OK, thanks much --what do I add to my sources list for the proposed
updates?  Do I need all the lines ending with main free etc. or just
one line?


On Sat, 01 Jul 2023 06:16:33 -0400,
Alexander V. Makartsev wrote:
> 
> [1  ]
> On 30.06.2023 03:11, John Covici wrote:
> > Hi.  I am trying to install odcb-mariadb in bookworm.  It was fine in
> > bullseye, but in bookworm I get the following error:
> > Unpacking odbc-mariadb (3.1.15-3) over (3.1.15-3) ...
> > Setting up odbc-mariadb (3.1.15-3) ...
> > odbcinst: SQLInstallDriverEx failed with Unable to find component
> > name.
> > dpkg: error processing package odbc-mariadb (--configure):
> > 
> > How to fix?
> > 
> > Thanks in advance for any suggestions.
> > 
> No errors on my system.
> You might need to add "bookworm-proposed-updates" repo to
> "/etc/apt/sources.list" and
> reinstall "odbcinst" "unixodbc-common" "odbc-mariadb" packages like so:
> 
>$ sudo apt update
>$ sudo apt install --reinstall unixodbc-common odbcinst odbc-mariadb
> 
> Backup "/etc/odbc.ini" and "/etc/odbcinst.ini" files before
> re-installation just in case.
> 
> 
> -- 
> With kindest regards, Alexander.
> 
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
> ⠈⠳⣄
> [2  ]

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

 John Covici wb2una
 cov...@ccs.covici.com

Re: cannot install odcb mariadb in bookworm

[Alexander V. Makartsev]

On 30.06.2023 03:11, John Covici wrote:

Hi.  I am trying to install odcb-mariadb in bookworm.  It was fine in
bullseye, but in bookworm I get the following error:
Unpacking odbc-mariadb (3.1.15-3) over (3.1.15-3) ...
Setting up odbc-mariadb (3.1.15-3) ...
odbcinst: SQLInstallDriverEx failed with Unable to find component
name.
dpkg: error processing package odbc-mariadb (--configure):

How to fix?

Thanks in advance for any suggestions.


No errors on my system.
You might need to add "bookworm-proposed-updates" repo to 
"/etc/apt/sources.list" and

reinstall "odbcinst" "unixodbc-common" "odbc-mariadb" packages like so:

   $ sudo apt update
   $ sudo apt install --reinstall unixodbc-common odbcinst odbc-mariadb

Backup "/etc/odbc.ini" and "/etc/odbcinst.ini" files before 
re-installation just in case.



--
With kindest regards, Alexander.

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

Re: Configuration asterisk

[BERTRAND Joël]

Bon, j'ai réussi à régler le coup des appels entrants. Le '.' et le '!'
ne peuvent pas être utilisés n'importe où et les regex sont un peu
tatillonnes.

Reste le problème des appels sortants :

[User-standard]
exten => 6001,1,Dial(SIP/6001)
exten => 6002,1,Dial(SIP/6002)
exten => _0.,1,Dial(SIP/${EXTEN:1})

retourne :
[Jul  1 12:00:13] WARNING[12569][C-0001] chan_sip.c: Purely numeric
hostname (0x), and not a peer--rejecting!
[Jul  1 12:00:13] NOTICE[12569][C-0001] app_dial.c: Unable to create
channel of type 'SIP' (cause 20 - Subscriber absent)

JKB

Configuration asterisk

[BERTRAND Joël]

Bonjour à tous,

Je tente la configuration d'un serveur asterisk et je me noie un peu
dans la configuration.

Ce que j'ai fait jusqu'à présent :
- installation d'un serveur asterisk (20.3.0~dfsg+~cs6.13.40431413-1) ;
- configuration du fichier users.conf pour rajouter tous mes téléphones
IP. Tous les téléphones sont connectés au serveur asterisk et tous
peuvent s'appeler entre eux.

Dans extensions.conf, j'ai simplement configuré :

[general]
static=yes
writeprotect=no
autofallthrough=yes
clearglobalvars=yes
priorityjumping=no

[globals]
dial_opts=g
my_dial_status=answer
timeout=45

[User-standard]
exten => 6001,1,Dial(SIP/6001)
exten => 6002,1,Dial(SIP/6002)
...

Je tente maintenant de connecter ce serveur asterisk à mon trunk SIP.
J'ai donc configuré dans sip.conf le compte correspondant au trunk SIP :

[general]
context=public
allowoverlap=no
udpbindaddr=192.168.1.1:5060
tcpenable=no
tcpbindaddr=0.0.0.0
transport=udp
srvlookup=yes
language=fr
register => 
localnet=192.168.0.0/255.255.0.0
directmedia=update,nonat
nat=force_rport,comedia
qualify=yes
externrefresh=15
directmediapermit=192.168.0.0/255.255.0.0
externaddr=
externtlsport=5060


Asterisk est content puisqu'il m'indique :
rayleigh*CLI> sip show registry
Hostdnsmgr Username   Refresh
StateReg.Time
:5070   N  trunk-sip@sy   105 Registered
  Sat, 01 Jul 2023 11:05:42
1 SIP registrations.

Maintenant, je cherche à pouvoir appeler le monde extérieur et à être
appelé et je sèche. Les appels sont bien routés vers mon serveur
asterisk puisque dans les logs, lorsque j'essaie de m'appeler, je vois
ceci :

[Jul  1 11:00:47] NOTICE[8977][C-0001] chan_sip.c: Call from ''
(37.97.65.186:5070) to extension '+33x' rejected because
extension not found in context 'public'.

Or j'ai rajouté dans le fichier extensions.conf :
exten => ,1,Dial(SIP/6001)
soit à la suite de [User-standard], soit dans un contexte [oublic]. Rien
n'y fait.

J'ai aussi essayé d'appeler l'extérieur avec une règle du type exten =>
_0.,1,Dial(SIP/${EXTEN:1}), même motif, même punition mais avec un autre
message d'erreur :

[Jul  1 11:13:10] WARNING[9644][C-0002] chan_sip.c: Purely numeric
hostname (0x), and not a peer--rejecting!

La question est donc relativement simple. Comment faire une
configuration simpliste d'asterisk pour le connecter au monde extérieur
? Je me perds dans la documentation (officielle ou non).

Merci de vos lumières,

JKB

Nettoyage du spam : juin 2023

[Jean-Pierre Giraud]

Bonjour,
Comme nous sommes en juillet, il est désormais possible de traiter les
archives du mois de juin 2023 des listes francophones.

N'oubliez bien sûr pas d'ajouter votre nom à la liste des relecteurs
pour que nous sachions où nous en sommes.

Détails du processus de nettoyage du spam sur :

https://wiki.debian.org/I18n/FrenchSpamClean

Jean-Pierre Giraud



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