Re: Thunderbird: cursor probleem

[Martijn van de Streek]

Paul van der Vlis schreef op ma 02-05-2022 om 16:02 [+0200]:
> Een klant van me heeft een raar probleem, als hij e-mail beantwoord
> in  Thunderbird dan is er vaak geen knipperende cursor. Hij kan wel
> wat typen, maar het is dus wat onduidelijk waar dat terecht komt.
> 
> Bij mailtjes van mij krijgt hij wel een cursor, maar ik stuur 
> platte-tekst mail. Misschien dat dat het verschil maakt.
> 
> Heeft iemand een idee wat dit zou kunnen zijn?

Heeft Thunderbird (net als browsers) een "caret mode"? (in browsers zet
je dit aan/uit met F7)

Dat is een feature voor toegankelijkheid, die als hij per ongeluk
aangezet wordt kan leiden tot onverwacht cursor-gedrag. 

-Martijn

Re: mariadb does not run

[tomas]

On Mon, May 02, 2022 at 10:44:58PM +0200, Lucio Crusca wrote:
> Il 02/05/22 17:43, Larry Martell ha scritto:
> > mysqld_safe is a shell script - you could try running it with sh -x to
> > see what it's doing and/or how it fails.
> 
> Here's to you:
> 

According to this huge mess, the log file is somewhere in
/var/lib/mysql/t470.err (the number '470' is the process
ID, aka PID, so it will change at every start).

Have you had a look at this?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: how to install gcc-6 in debian bullseye

[tomas]

On Mon, May 02, 2022 at 11:51:02PM +0300, Georgi Naplatanov wrote:
> On 5/2/22 23:25, michaelmorgan...@gmail.com wrote:
> > Can anyone kindly instruct me how to install gcc-6 in Debian 11? I need
> > compile a software and was hinted gcc version (10) is too high. I have
> > old machine with gcc 6 and was able to compile it there.
> > 
> 
> It seems that Debian 9 has gcc-6 so you can use Docker image with Debian 9.

Alternatively, build in a chroot, using archives.debian.org as
source (that's what I do; for convenience I use schroot, but
am not really sure whether to keep it). The Debian Wiki [1]
has a good starting point.

Cheers

[1] https://wiki.debian.org/chroot
-- 
t


signature.asc
Description: PGP signature

process for getting dbgsym packages updated

[Mike Kupfer]

On Debian 11.3, I've discovered that I can reliably get a core file from
/usr/lib/x86_64-linux-gnu/webkit2gtk-4.0/WebKitWebProcess by using Atril
to view a PDF file (any PDF file that I've tried).  But the dbgsym
packages for libwebkit2gtk-4.0-37 and libjavascriptcoregtk-4.0-18
(version 2.34.6-1~deb11u1) do not match the installed libraries (version
2.36.0-3~deb11u1).

Is there a process for getting the dbgsym packages updated?

thanks,
mike

Re: Wi-Fi USB dongle disconnects

[riveravaldez]

On 5/2/22, David Wright  wrote:
> On Mon 02 May 2022 at 12:26:44 (-0300), riveravaldez wrote:
>> Hi, I'm using a USB dongle to connect an old desktop machine (updated
>> debian-stable) to my home-WLAN (Wi-Fi).
>>
>> This is the hardware:
>>
>> ```
>> $ sudo lsusb -v
>> Bus 001 Device 007: ID 148f:7601 Ralink Technology, Corp. MT7601U
>> Wireless Adapter
>> Device Descriptor:
>>   bLength18
>>   bDescriptorType 1
>>   bcdUSB   2.01
>>   bDeviceClass0
>>   bDeviceSubClass 0
>>   bDeviceProtocol 0
>>   bMaxPacketSize064
>>   idVendor   0x148f Ralink Technology, Corp.
>>   idProduct  0x7601 MT7601U Wireless Adapter
>>   bcdDevice0.00
>>   iManufacturer   1 MediaTek
>>   iProduct2 802.11 n WLAN
>>   iSerial 3 1.0
>> (...)
>> ```
>>
>> Working fine til just now, then (after system upgrade) it stop giving
>
> Does "system upgrade" mean more than, say, apt-get upgrade?

Hi, David, and thanks a lot for your help!

Literally means:

$ sudo apt-get update && sudo apt-get dist-upgrade

Afterwards:

$ sudo apt-get autoclean && sudo apt-get autoremove

This is what I do normally.

>> me connection (ip route: nothing).
>>
>> I tried to ifup the interface:
>>
>> ```
>> $ sudo ifup wlan0
>> [sudo] password for desktop:
>> Internet Systems Consortium DHCP Client 4.4.1
>> Copyright 2004-2018 Internet Systems Consortium.
>> All rights reserved.
>> For info, please visit https://www.isc.org/software/dhcp/
>>
>> Cannot find device "wlan0"
>> Failed to get interface index: No such device
>>
>> If you think you have received this message due to a bug rather
>> than a configuration issue please read the section on submitting
>> bugs on either our web page at www.isc.org or in the README file
>> before submitting a bug.  These pages explain the proper
>> process and the information we find helpful for debugging.
>>
>> exiting.
>> ifup: failed to bring up wlan0
>> ```
>>
>> Then checked journalctl:
>>
>> ```
>> $ sudo journalctl -b -exp3
>> (...)
>> may 02 10:35:04 debian kernel: usb usb1-port2: disabled by hub (EMI?),
>> re-enabling...
>> may 02 10:35:04 debian kernel: mt7601u 1-2:1.0: mt7601u_rxdc_cal timed
>> out
>> may 02 10:35:04 debian dhclient[1141]: receive_packet failed on wlan0:
>> Network is down
>> may 02 10:35:06 debian systemd-udevd[6026]: wlan0: Failed to get link
>> config: No such device
>> may 02 10:35:07 debian systemd-udevd[6061]: wlan1: Failed to rename
>> network interface 6 from 'wlan1' to 'wlx20e9170d5d9e': Device or
>> resource busy
>
> I recognise that MAC.

I am greatly and happily surprised.

> You posted about it in January. You were running
> it with iwd.

Indeed^2.

> Why is systemd-udevd trying to rename the interface?

Have no idea. Maybe I did something in an improper fashion...
In fact, can't recall touching nothing about systemd-udevd.
Should I?

> Do you still have the file:
>
> $ cat /lib/systemd/network/80-iwd.link
> [Match]
> Type=wlan
>
> [Link]
> NamePolicy=keep kernel  ←
> $
>
> or your own version under /etc?

I still have the file:

```
$ cat /lib/systemd/network/80-iwd.link
[Match]
Type=wlan

[Link]
NamePolicy=keep kernel
```

And in /etc I only found:

$ sudo ls -aR /etc/ | grep iwd
iwd
/etc/iwd:
iwd.service

But nothing I remember to have created (at least manually).

> Or has the upgrade tried to revert the system back to a more
> conventional ifupdown/wpa configuration in some way?

Maybe, that's one of the things I'm trying to rule out/discard,
but can't think/know of a way to check it.

If the USB-port makes an unstable contact, could that connect/
/disconnect make the system assign new name to the dongle in
each iteration? (Just an idea...)

It has not happened again since the last occurrence, couple of
hours ago.

>> may 02 10:35:08 debian dhclient[6067]: Failed to get interface index:
>> No such device
>> may 02 10:35:08 debian dhclient[6067]:
>> may 02 10:35:08 debian dhclient[6067]: If you think you have received
>> this message due to a bug rather
>> may 02 10:35:08 debian dhclient[6067]: than a configuration issue
>> please read the section on submitting
>> may 02 10:35:08 debian dhclient[6067]: bugs on either our web page at
>> www.isc.org or in the README file
>> may 02 10:35:08 debian dhclient[6067]: before submitting a bug.  These
>> pages explain the proper
>> may 02 10:35:08 debian dhclient[6067]: process and the information we
>> find helpful for debugging.
>> may 02 10:35:08 debian dhclient[6067]:
>> may 02 10:35:08 debian dhclient[6067]: exiting.
>> (...)
>> ```
>>
>> Tried renaming the interface with:
>>
>> $ sudo ip link set wlan1 name wlan0
>>
>> But it was unable to connect:
>>
>> ```
>> $ sudo ifup wlan0
>> Internet Systems Consortium DHCP Client 4.4.1
>> Copyright 2004-2018 Internet Systems Consortium.
>> All rights reserved.
>> For info, please visit https://www.isc.org/software/dhcp/
>>
>> Listening on 

Re: mutt upgrade in testing broke, downgrade worked

[songbird]

Greg Wooledge wrote:
...
> The only difference between package versions 2.2.3-1 and 2.2.3-2 is
> the patch set that Debian applies.


  ok, thanks, i filed a bug report.


  songbird

Re: mutt upgrade in testing broke, downgrade worked

[Greg Wooledge]

On Mon, May 02, 2022 at 05:58:31PM -0400, songbird wrote:
> > On Mon, May 02, 2022 at 11:23:58AM -0400, songbird wrote:
> >> 2.2.3-1 version works
> >> 2.2.3-2 version does not work
> >
> > This isn't a useful bug report until you say *how* version 2.2.3-2 fails.
> 
>   mutt doesn't send mail.

*sigh*

OK, I give up.  I see no way to get useful information out of you.

>   an FYI to fellow users can be helpful.  the error has been
> reported to the mutt mailing list, but gmane doesn't go through
> to that list.  i don't think it's a problem of Debian itself

The UPSTREAM part of the package version (2.2.3) is the same between
the two packages.

The only difference between package versions 2.2.3-1 and 2.2.3-2 is
the patch set that Debian applies.

Re: mutt upgrade in testing broke, downgrade worked

[songbird]

Greg Wooledge wrote:
> On Mon, May 02, 2022 at 11:23:58AM -0400, songbird wrote:
>> 
>> 2.2.3-1 version works
>> 2.2.3-2 version does not work
>
> This isn't a useful bug report until you say *how* version 2.2.3-2 fails.

  mutt doesn't send mail.


> Also, bugs should be reported to bugs.debian.org, not here.

  an FYI to fellow users can be helpful.  the error has been
reported to the mutt mailing list, but gmane doesn't go through
to that list.  i don't think it's a problem of Debian itself
so no need to raise it to that level yet.  it is after all
testing.


  songbird

Re: how to install gcc-6 in debian bullseye

[Georgi Naplatanov]

On 5/2/22 23:25, michaelmorgan...@gmail.com wrote:
> Can anyone kindly instruct me how to install gcc-6 in Debian 11? I need
> compile a software and was hinted gcc version (10) is too high. I have
> old machine with gcc 6 and was able to compile it there.
> 

It seems that Debian 9 has gcc-6 so you can use Docker image with Debian 9.

HTH

Kind regards
Georgi

Re: mariadb does not run

[Lucio Crusca]

Il 02/05/22 17:43, Larry Martell ha scritto:

mysqld_safe is a shell script - you could try running it with sh -x to
see what it's doing and/or how it fails.


Here's to you:


# bash -x mysqld_safe
+ KILL_MYSQLD=1
+ MYSQLD=
+ niceness=0
+ nowatch=0
+ mysqld_ld_preload=
+ mysqld_ld_library_path=
+ flush_caches=0
+ numa_interleave=0
+ wsrep_on=0
+ dry_run=0
+ defaults_group_suffix=
+ logging=init
+ want_syslog=0
+ syslog_tag=
+ user=mysql
+ group=mysql
+ pid_file=
+ err_log=
+ err_log_base=
+ skip_err_log=0
+ syslog_tag_mysqld=mysqld
+ syslog_tag_mysqld_safe=mysqld_safe
+ trap '' 1 2 3 15
+ umask 007
+ UMASK=0640
++ echo 0640
++ sed -e 's/[^0246]//g'
+ fmode=0640
++ echo 0640
++ cut -c1
+ octalp=0
++ echo 0640
++ wc -c
++ sed -e 's/ //g'
+ fmlen=5
+ '[' x0 '!=' x0 -o x0640 '!=' x0640 -o x5 '!=' x5 ']'
++ cut -c3-4
++ echo 0640
+ fmode=40
+ fmode=640
+ '[' x0640 '!=' x0640 ']'
+ defaults=
+ case "$1" in
+ wsrep_start_position_opt=
++ dirname mysqld_safe
+ MY_PWD=.
++ cd ./..
++ pwd
+ MY_PWD=/
+ test -n '' -a -d ''
+ test -x //bin/mariadbd
+ test -x //libexec/mariadbd
+ test -x //sbin/mariadbd
+ MY_BASEDIR_VERSION=/
+ ledir=//sbin
++ find_in_bin mariadbd-safe-helper
++ test -x //bin/mariadbd-safe-helper
++ echo //bin/mariadbd-safe-helper
+ helper=//bin/mariadbd-safe-helper
++ find_in_bin my_print_defaults
++ test -x //bin/my_print_defaults
++ echo //bin/my_print_defaults
+ print_defaults=//bin/my_print_defaults
+ command -v //bin/mariadbd-safe-helper --help
+ helper_exist=0
+ test -d //data/mysql
+ test -d //var/mysql
+ DATADIR=/var/lib/mysql
+ test -z ''
+ test -r /var/lib/mysql/my.cnf
+ MYSQL_HOME=/
+ export MYSQL_HOME
+ args=
+ SET_USER=2
++ //bin/my_print_defaults --loose-verbose --mysqld
+ parse_arguments
+ test 2 -eq 2
+ SET_USER=0
+ unrecognized_handling=complain
++ //bin/my_print_defaults --loose-verbose mysqld_safe safe_mysqld 
mariadb_safe mariadbd-safe

+ parse_arguments
+ unrecognized_handling=collect
+ parse_arguments
+ '[' -n '' ']'
+ for dir in lib64/mysql/plugin lib64/plugin lib/mysql/plugin lib/plugin
+ '[' -d //lib64/mysql/plugin ']'
+ for dir in lib64/mysql/plugin lib64/plugin lib/mysql/plugin lib/plugin
+ '[' -d //lib64/plugin ']'
+ for dir in lib64/mysql/plugin lib64/plugin lib/mysql/plugin lib/plugin
+ '[' -d //lib/mysql/plugin ']'
+ plugin_dir=//lib/mysql/plugin
+ break
+ '[' -z //lib/mysql/plugin ']'
+ plugin_dir=//lib/mysql/plugin
+ '[' 0 -eq 1 ']'
+ '[' 0 -eq 1 ']'
+ '[' -n '' -o 0 -eq 0 ']'
+ '[' -n '' ']'
+ '[' -n '' ']'
++ uname -n
+ err_log=/var/lib/mysql/t470.err
+ append_arg_to_args --log-error=/var/lib/mysql/t470.err
++ shell_quote_string --log-error=/var/lib/mysql/t470.err
++ echo --log-error=/var/lib/mysql/t470.err
++ sed -e 's,\([^a-zA-Z0-9/_.=-]\),\\\1,g'
+ args=' --log-error=/var/lib/mysql/t470.err'
+ '[' 0 -eq 1 ']'
+ log_notice 'Logging to '\''/var/lib/mysql/t470.err'\''.'
+ log_generic daemon.notice 'Logging to '\''/var/lib/mysql/t470.err'\''.'
+ '[' 0 -eq 1 ']'
+ priority=daemon.notice
+ shift
++ date '+%y%m%d %H:%M:%S'
+ msg='220502 22:36:41 mysqld_safe Logging to 
'\''/var/lib/mysql/t470.err'\''.'
+ echo '220502 22:36:41 mysqld_safe Logging to 
'\''/var/lib/mysql/t470.err'\''.'

220502 22:36:41 mysqld_safe Logging to '/var/lib/mysql/t470.err'.
+ case $logging in
+ logging=file
+ USER_OPTION=
+ test -w / -o root = root
+ test mysql '!=' root -o 0 = 1
+ USER_OPTION=--user=mysql
+ GROUP_OPTION=--group=mysql
+ test -n ''
+ test -n ''
+ safe_mysql_unix_port=/run/mysqld/mysqld.sock
++ dirname /run/mysqld/mysqld.sock
+ mysql_unix_port_dir=/run/mysqld
+ '[' '!' -d /run/mysqld -a 0 -eq 0 ']'
+ test -z ''
+ MYSQLD=mariadbd
+ test '!' -x //sbin/mariadbd
+ test -z ''
++ uname -n
+ pid_file=t470.pid
+ append_arg_to_args --pid-file=t470.pid
++ shell_quote_string --pid-file=t470.pid
++ echo --pid-file=t470.pid
++ sed -e 's,\([^a-zA-Z0-9/_.=-]\),\\\1,g'
+ args=' --log-error=/var/lib/mysql/t470.err --pid-file=t470.pid'
+ case "$pid_file" in
+ pid_file=/var/lib/mysql/t470.pid
+ test -n ''
+ test -n ''
+ test 0 -eq 0
+ NOHUP_NICENESS=nohup
+ nohup nice
++ nice
+ normal_niceness=0
++ nohup nice
+ nohup_niceness=0
+ numeric_nice_values=1
+ for val in $normal_niceness $nohup_niceness
+ case "$val" in
+ for val in $normal_niceness $nohup_niceness
+ case "$val" in
+ test 1 -eq 1
++ expr 0 - 0
+ nice_value_diff=0
+ test 1 -eq 0
+ test -n ''
+ test -f /var/lib/mysql/t470.pid
+ true
+ test 0 -eq 1
+ test 0 -eq 1
++ mysqld_ld_preload_text
++ text=
++ '[' -n '' ']'
++ '[' -n '' ']'
++ echo ''
+ cmd=nohup
+ '[' 0 -eq 1 ']'
+ true
+ test 0 -eq 1
+ test 0 -eq 1
+ for i in "$ledir/$MYSQLD" "$defaults_group_suffix" "$defaults" 
"--basedir=$MY_BASEDIR_VERSION" "--datadir=$DATADIR" 
"--plugin-dir=$plugin_dir" "$USER_OPTION"

++ shell_quote_string //sbin/mariadbd
++ echo //sbin/mariadbd
++ sed -e 's,\([^a-zA-Z0-9/_.=-]\),\\\1,g'
+ cmd='nohup //sbin/mariadbd'
+ for i in "$ledir/$MYSQLD" "$defaults_group_suffix" "$defaults" 
"--basedir=$MY_BASEDIR_VERSION" "--datadir=$DATADIR" 

Re: how to install gcc-6 in debian bullseye

[Greg Wooledge]

On Mon, May 02, 2022 at 03:25:20PM -0500, michaelmorgan...@gmail.com wrote:
> Can anyone kindly instruct me how to install gcc-6 in Debian 11? I need
> compile a software and was hinted gcc version (10) is too high. I have
> old machine with gcc 6 and was able to compile it there. 

Stop looking at packages.  Download the source code for gcc 6, and build
it as if it were a foreign program.  Install it in /usr/local or
/opt/something as if it were a foreign program.

Or, fix the program you're trying to compile, because it's clearly full
of bugs that older gcc simply wasn't catching.

how to install gcc-6 in debian bullseye

[michaelmorgan937]

Can anyone kindly instruct me how to install gcc-6 in Debian 11? I need
compile a software and was hinted gcc version (10) is too high. I have
old machine with gcc 6 and was able to compile it there. 

 

Thank you very much.

Michael

 

 

Re: Wi-Fi USB dongle disconnects

[David Wright]

On Mon 02 May 2022 at 12:26:44 (-0300), riveravaldez wrote:
> Hi, I'm using a USB dongle to connect an old desktop machine (updated
> debian-stable) to my home-WLAN (Wi-Fi).
> 
> This is the hardware:
> 
> ```
> $ sudo lsusb -v
> Bus 001 Device 007: ID 148f:7601 Ralink Technology, Corp. MT7601U
> Wireless Adapter
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   2.01
>   bDeviceClass0
>   bDeviceSubClass 0
>   bDeviceProtocol 0
>   bMaxPacketSize064
>   idVendor   0x148f Ralink Technology, Corp.
>   idProduct  0x7601 MT7601U Wireless Adapter
>   bcdDevice0.00
>   iManufacturer   1 MediaTek
>   iProduct2 802.11 n WLAN
>   iSerial 3 1.0
> (...)
> ```
> 
> Working fine til just now, then (after system upgrade) it stop giving

Does "system upgrade" mean more than, say, apt-get upgrade?

> me connection (ip route: nothing).
> 
> I tried to ifup the interface:
> 
> ```
> $ sudo ifup wlan0
> [sudo] password for desktop:
> Internet Systems Consortium DHCP Client 4.4.1
> Copyright 2004-2018 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Cannot find device "wlan0"
> Failed to get interface index: No such device
> 
> If you think you have received this message due to a bug rather
> than a configuration issue please read the section on submitting
> bugs on either our web page at www.isc.org or in the README file
> before submitting a bug.  These pages explain the proper
> process and the information we find helpful for debugging.
> 
> exiting.
> ifup: failed to bring up wlan0
> ```
> 
> Then checked journalctl:
> 
> ```
> $ sudo journalctl -b -exp3
> (...)
> may 02 10:35:04 debian kernel: usb usb1-port2: disabled by hub (EMI?),
> re-enabling...
> may 02 10:35:04 debian kernel: mt7601u 1-2:1.0: mt7601u_rxdc_cal timed out
> may 02 10:35:04 debian dhclient[1141]: receive_packet failed on wlan0:
> Network is down
> may 02 10:35:06 debian systemd-udevd[6026]: wlan0: Failed to get link
> config: No such device
> may 02 10:35:07 debian systemd-udevd[6061]: wlan1: Failed to rename
> network interface 6 from 'wlan1' to 'wlx20e9170d5d9e': Device or
> resource busy

I recognise that MAC. You posted about it in January. You were running
it with iwd. Why is systemd-udevd trying to rename the interface?
Do you still have the file:

$ cat /lib/systemd/network/80-iwd.link
[Match]
Type=wlan

[Link]
NamePolicy=keep kernel  ←
$ 

or your own version under /etc?

Or has the upgrade tried to revert the system back to a more
conventional ifupdown/wpa configuration in some way?

> may 02 10:35:08 debian dhclient[6067]: Failed to get interface index:
> No such device
> may 02 10:35:08 debian dhclient[6067]:
> may 02 10:35:08 debian dhclient[6067]: If you think you have received
> this message due to a bug rather
> may 02 10:35:08 debian dhclient[6067]: than a configuration issue
> please read the section on submitting
> may 02 10:35:08 debian dhclient[6067]: bugs on either our web page at
> www.isc.org or in the README file
> may 02 10:35:08 debian dhclient[6067]: before submitting a bug.  These
> pages explain the proper
> may 02 10:35:08 debian dhclient[6067]: process and the information we
> find helpful for debugging.
> may 02 10:35:08 debian dhclient[6067]:
> may 02 10:35:08 debian dhclient[6067]: exiting.
> (...)
> ```
> 
> Tried renaming the interface with:
> 
> $ sudo ip link set wlan1 name wlan0
> 
> But it was unable to connect:
> 
> ```
> $ sudo ifup wlan0
> Internet Systems Consortium DHCP Client 4.4.1
> Copyright 2004-2018 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
> 
> Listening on LPF/wlan0/20:e9:17:0d:5d:9e
> Sending on   LPF/wlan0/20:e9:17:0d:5d:9e
> Sending on   Socket/fallback
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> ```
> 
> Apparently until I restarted iwd.service and tried again.
> 
> And this is all I have in dmesg that seems relevant:
> 
> ```
> $ sudo dmesg
> (...)
> [   12.219824] usb 1-2: reset high-speed USB device number 2 using ehci-pci
> [   12.236267] EXT4-fs (sda3): mounted filesystem with ordered data
> mode. Opts: (null)
> [   12.382723] mt7601u 1-2:1.0: ASIC revision: 76010001 MAC revision: 76010500
> [   12.424352] mt7601u 1-2:1.0: EEPROM ver:0d fae:00
> [   12.499390] EXT4-fs (sdb1): mounted filesystem with ordered data
> mode. Opts: (null)
> [   12.654265] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
> [   12.655016] usbcore: 

Re: Odd reproducible problem - but is it a bug?

[tomas]

On Mon, May 02, 2022 at 07:58:12PM +0200, Michael Lange wrote:
> Hi,
> 
> On Mon, 2 May 2022 10:17:06 -0500
> Richard Owlett  wrote:
> 
> > I'm using Debian 10.7 with MATE DE [will be updated later this week]
> > The machine is a Lenovo T510 and is setup to login as either "richard" 
> > or "root".
> > 
> > If logged in as "richard" I can execute su {+ password} and receive a 
> > prompt indicating I'm "root".
> > 
> > However if I then enter "update-grub", the response is
> >"bash: update-grub: command not found"
> > as if I were the unprivileged user "richard".
> 
> you need to do 
> 
>  # su -
> 
> (instead of just
> 
>  # su
> ),
> otherwise $PATH will be inherited from user "richard" and thus lack the
> entry "/sbin".

Or just get used to say "/sbin/update-grub" ;-)

(No, I'm not really being serious here. But half-acquiring this
habit would have helped you to unravel the problem like in "Ah,
I have the permissions but not the $PATH..."

It's no different from the TVs of yore: is it the driver stage
to the high voltage, or did just the capacitor short? What can
I do to tell apart those two?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: Odd reproducible problem - but is it a bug?

[Michael Lange]

Hi,

On Mon, 2 May 2022 10:17:06 -0500
Richard Owlett  wrote:

> I'm using Debian 10.7 with MATE DE [will be updated later this week]
> The machine is a Lenovo T510 and is setup to login as either "richard" 
> or "root".
> 
> If logged in as "richard" I can execute su {+ password} and receive a 
> prompt indicating I'm "root".
> 
> However if I then enter "update-grub", the response is
>"bash: update-grub: command not found"
> as if I were the unprivileged user "richard".

you need to do 

 # su -

(instead of just

 # su
),
otherwise $PATH will be inherited from user "richard" and thus lack the
entry "/sbin".

Have a nice day,

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Ahead warp factor one, Mr. Sulu.

Re: Wi-Fi USB dongle disconnects

[riveravaldez]

Hi, it just happened again.

'wlan0' is no more, instead I have 'wlan2'. Apparently this fixes it (manually):

```
$ sudo ifconfig
[sudo] password for desktop:
lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 65  bytes 7952 (7.7 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 65  bytes 7952 (7.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan2: flags=4163  mtu 1500
inet6 fe80::22e9:17ff:fe0d:5d9e  prefixlen 64  scopeid 0x20
ether 20:e9:17:0d:5d:9e  txqueuelen 1000  (Ethernet)
RX packets 198  bytes 32709 (31.9 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 130  bytes 17331 (16.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ ip route
$ sudo ip link set wlan2 down
$ sudo ifconfig
lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 65  bytes 7952 (7.7 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 65  bytes 7952 (7.7 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

$ sudo ip link set wlan2 name wlan0
$ sudo ifup wlan0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/20:e9:17:0d:5d:9e
Sending on   LPF/wlan0/20:e9:17:0d:5d:9e
Sending on   Socket/fallback
DHCPREQUEST for 192.168.0.164 on wlan0 to 255.255.255.255 port 67
DHCPREQUEST for 192.168.0.164 on wlan0 to 255.255.255.255 port 67
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 192.168.0.164 from 192.168.0.1
DHCPREQUEST for 192.168.0.164 on wlan0 to 255.255.255.255 port 67
DHCPACK of 192.168.0.164 from 192.168.0.1
bound to 192.168.0.164 -- renewal in 1607 seconds.
$ ip route
default via 192.168.0.1 dev wlan0
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.164
```

Any idea why the name-change and how to solve this?

Thanks again.


On 5/2/22, riveravaldez  wrote:
> Hi, I'm using a USB dongle to connect an old desktop machine (updated
> debian-stable) to my home-WLAN (Wi-Fi).
>
> This is the hardware:
>
> ```
> $ sudo lsusb -v
> Bus 001 Device 007: ID 148f:7601 Ralink Technology, Corp. MT7601U
> Wireless Adapter
> Device Descriptor:
>   bLength18
>   bDescriptorType 1
>   bcdUSB   2.01
>   bDeviceClass0
>   bDeviceSubClass 0
>   bDeviceProtocol 0
>   bMaxPacketSize064
>   idVendor   0x148f Ralink Technology, Corp.
>   idProduct  0x7601 MT7601U Wireless Adapter
>   bcdDevice0.00
>   iManufacturer   1 MediaTek
>   iProduct2 802.11 n WLAN
>   iSerial 3 1.0
> (...)
> ```
>
> Working fine til just now, then (after system upgrade) it stop giving
> me connection (ip route: nothing).
>
> I tried to ifup the interface:
>
> ```
> $ sudo ifup wlan0
> [sudo] password for desktop:
> Internet Systems Consortium DHCP Client 4.4.1
> Copyright 2004-2018 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
>
> Cannot find device "wlan0"
> Failed to get interface index: No such device
>
> If you think you have received this message due to a bug rather
> than a configuration issue please read the section on submitting
> bugs on either our web page at www.isc.org or in the README file
> before submitting a bug.  These pages explain the proper
> process and the information we find helpful for debugging.
>
> exiting.
> ifup: failed to bring up wlan0
> ```
>
> Then checked journalctl:
>
> ```
> $ sudo journalctl -b -exp3
> (...)
> may 02 10:35:04 debian kernel: usb usb1-port2: disabled by hub (EMI?),
> re-enabling...
> may 02 10:35:04 debian kernel: mt7601u 1-2:1.0: mt7601u_rxdc_cal timed out
> may 02 10:35:04 debian dhclient[1141]: receive_packet failed on wlan0:
> Network is down
> may 02 10:35:06 debian systemd-udevd[6026]: wlan0: Failed to get link
> config: No such device
> may 02 10:35:07 debian systemd-udevd[6061]: wlan1: Failed to rename
> network interface 6 from 'wlan1' to 'wlx20e9170d5d9e': Device or
> resource busy
> may 02 10:35:08 debian dhclient[6067]: Failed to get interface index:
> No such device
> may 02 10:35:08 debian dhclient[6067]:
> may 02 10:35:08 debian dhclient[6067]: If you think you have received
> this message due to a bug rather
> may 02 10:35:08 debian dhclient[6067]: than a configuration issue
> please read the section on submitting
> may 02 10:35:08 debian dhclient[6067]: bugs on either our web page at
> www.isc.org or in the README file
> may 02 10:35:08 debian 

Re: file born 30 seconds after its creation on ext4 - bug?

[tomas]

On Mon, May 02, 2022 at 10:04:00AM -0500, David Wright wrote:

> I'm not very familiar with files' birth as it's a relatively new
> addition to filesystems, particularly how to display it even when
> present. So I looked it up, and the ext4 wiki says it's the time
> at which the inode is created. I also read in ext4 wikipedia:

[...]

> So I wondered whether a delayed birth time could be caused by the
> filesystem waiting a while before it actually starts creating any
> allocation for the file on the disk. Having amassed some data,
> depending on its size, it decides where it's going to write it,
> ie which block group. Only then does it create the file's inode,
> so that it can keep file contents and inode close together.

That actually makes sense. It would be surprising behaviour,
but at least whithin reach; whether it's intentional or may be
considered a bug is, of course, another thing

Thanks for diving into details, cheers
-- 
t


signature.asc
Description: PGP signature

Re: Odd reproducible problem - but is it a bug?

[Greg Wooledge]

On Mon, May 02, 2022 at 03:43:41PM +, Andrew M.A. Cater wrote:
> Not bug - feature.

I disagree.  Strongly.  It is a CHANGE, but it is not a feature.

> See also su -
> 
> It's in the release notes, I'm fairly sure.

It's also at .  It has also
been discussed to death and beyond on this mailing list.  Literally
dozens, if not hundreds, of message have been posted about it over the
last couple years.

The fact that the OP never read any of them somehow fails to surprise me.

(Almost as much as the Debian maintainers refusing to ship a one-line
/etc/default/su file to fix the behavior of su fails to surprise me at
this point.  Fortunately, we can create that file ourselves and get
things back to normal.)

Re: mariadb does not run

[Larry Martell]

On Mon, May 2, 2022 at 11:38 AM Lucio Crusca  wrote:
>
> Il 02/05/22 15:46, to...@tuxteam.de ha scritto:
> > Have you tried to start the mariadb server by hand?
>
> Yes, I've tried with:
>
> # mysqld_safe
>
> but it exits almost immediately and it logs the same errors reported by
> `systemd status mariadb`

mysqld_safe is a shell script - you could try running it with sh -x to
see what it's doing and/or how it fails.

Re: Odd reproducible problem - but is it a bug?

[Andrew M.A. Cater]

On Mon, May 02, 2022 at 10:17:06AM -0500, Richard Owlett wrote:
> I'm using Debian 10.7 with MATE DE [will be updated later this week]
> The machine is a Lenovo T510 and is setup to login as either "richard" or
> "root".
> 
> If logged in as "richard" I can execute su {+ password} and receive a prompt
> indicating I'm "root".
> 
> However if I then enter "update-grub", the response is
>   "bash: update-grub: command not found"
> as if I were the unprivileged user "richard".
> 
> All is normal if I had initially been "root" or had become "root" via
> System -> Log Out richard  .
> 
> Bug?
> 
>

Hi Richard,

Not bug - feature. See also su -

It's in the release notes, I'm fairly sure.

All the very best, as ever,

Andy Cater 

Re: Odd reproducible problem - but is it a bug?

[Lucio Crusca]

Il 02/05/22 17:17, Richard Owlett ha scritto:
If logged in as "richard" I can execute su {+ password} and receive a 
prompt indicating I'm "root".


   "bash: update-grub: command not found"

Bug?



No, it's only an effect of the PATH variable. Try "su -".

Re: mutt upgrade in testing broke, downgrade worked

[Greg Wooledge]

On Mon, May 02, 2022 at 11:23:58AM -0400, songbird wrote:
> 
> 2.2.3-1 version works
> 2.2.3-2 version does not work

This isn't a useful bug report until you say *how* version 2.2.3-2 fails.

Also, bugs should be reported to bugs.debian.org, not here.

Re: mariadb does not run

[Lucio Crusca]

Il 02/05/22 15:46, to...@tuxteam.de ha scritto:

Have you tried to start the mariadb server by hand?


Yes, I've tried with:

# mysqld_safe

but it exits almost immediately and it logs the same errors reported by 
`systemd status mariadb`

Odd reproducible problem - but is it a bug?

[Richard Owlett]

I'm using Debian 10.7 with MATE DE [will be updated later this week]
The machine is a Lenovo T510 and is setup to login as either "richard" 
or "root".


If logged in as "richard" I can execute su {+ password} and receive a 
prompt indicating I'm "root".


However if I then enter "update-grub", the response is
  "bash: update-grub: command not found"
as if I were the unprivileged user "richard".

All is normal if I had initially been "root" or had become "root" via
System -> Log Out richard  .

Bug?

Wi-Fi USB dongle disconnects

[riveravaldez]

Hi, I'm using a USB dongle to connect an old desktop machine (updated
debian-stable) to my home-WLAN (Wi-Fi).

This is the hardware:

```
$ sudo lsusb -v
Bus 001 Device 007: ID 148f:7601 Ralink Technology, Corp. MT7601U
Wireless Adapter
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.01
  bDeviceClass0
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x148f Ralink Technology, Corp.
  idProduct  0x7601 MT7601U Wireless Adapter
  bcdDevice0.00
  iManufacturer   1 MediaTek
  iProduct2 802.11 n WLAN
  iSerial 3 1.0
(...)
```

Working fine til just now, then (after system upgrade) it stop giving
me connection (ip route: nothing).

I tried to ifup the interface:

```
$ sudo ifup wlan0
[sudo] password for desktop:
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Cannot find device "wlan0"
Failed to get interface index: No such device

If you think you have received this message due to a bug rather
than a configuration issue please read the section on submitting
bugs on either our web page at www.isc.org or in the README file
before submitting a bug.  These pages explain the proper
process and the information we find helpful for debugging.

exiting.
ifup: failed to bring up wlan0
```

Then checked journalctl:

```
$ sudo journalctl -b -exp3
(...)
may 02 10:35:04 debian kernel: usb usb1-port2: disabled by hub (EMI?),
re-enabling...
may 02 10:35:04 debian kernel: mt7601u 1-2:1.0: mt7601u_rxdc_cal timed out
may 02 10:35:04 debian dhclient[1141]: receive_packet failed on wlan0:
Network is down
may 02 10:35:06 debian systemd-udevd[6026]: wlan0: Failed to get link
config: No such device
may 02 10:35:07 debian systemd-udevd[6061]: wlan1: Failed to rename
network interface 6 from 'wlan1' to 'wlx20e9170d5d9e': Device or
resource busy
may 02 10:35:08 debian dhclient[6067]: Failed to get interface index:
No such device
may 02 10:35:08 debian dhclient[6067]:
may 02 10:35:08 debian dhclient[6067]: If you think you have received
this message due to a bug rather
may 02 10:35:08 debian dhclient[6067]: than a configuration issue
please read the section on submitting
may 02 10:35:08 debian dhclient[6067]: bugs on either our web page at
www.isc.org or in the README file
may 02 10:35:08 debian dhclient[6067]: before submitting a bug.  These
pages explain the proper
may 02 10:35:08 debian dhclient[6067]: process and the information we
find helpful for debugging.
may 02 10:35:08 debian dhclient[6067]:
may 02 10:35:08 debian dhclient[6067]: exiting.
(...)
```

Tried renaming the interface with:

$ sudo ip link set wlan1 name wlan0

But it was unable to connect:

```
$ sudo ifup wlan0
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/20:e9:17:0d:5d:9e
Sending on   LPF/wlan0/20:e9:17:0d:5d:9e
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
```

Apparently until I restarted iwd.service and tried again.

And this is all I have in dmesg that seems relevant:

```
$ sudo dmesg
(...)
[   12.219824] usb 1-2: reset high-speed USB device number 2 using ehci-pci
[   12.236267] EXT4-fs (sda3): mounted filesystem with ordered data
mode. Opts: (null)
[   12.382723] mt7601u 1-2:1.0: ASIC revision: 76010001 MAC revision: 76010500
[   12.424352] mt7601u 1-2:1.0: EEPROM ver:0d fae:00
[   12.499390] EXT4-fs (sdb1): mounted filesystem with ordered data
mode. Opts: (null)
[   12.654265] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   12.655016] usbcore: registered new interface driver mt7601u
[   12.757239] mt7601u 1-2:1.0 wlx20e9170d5d9e: renamed from wlan0
(...)
[   14.305151] NET: Registered protocol family 38
[   14.761139] cryptd: max_cpu_qlen set to 1000
[   15.106086] alg: No test for hmac(md4) (hmac(md4-generic))
[   15.179675] forcedeth :00:07.0 enp0s7: MSI enabled
[   15.179900] forcedeth :00:07.0 enp0s7: no link during initialization
[   16.175429] wlan0: authenticate with b8:66:85:fd:0a:d1
[   16.208493] wlan0: send auth to b8:66:85:fd:0a:d1 (try 1/3)
[   16.210114] wlan0: authenticated
[   16.211825] wlan0: associate with b8:66:85:fd:0a:d1 (try 1/3)
[   16.217859] wlan0: RX AssocResp from b8:66:85:fd:0a:d1 (capab=0x411
status=0 aid=5)
[   16.253727] wlan0: associated
[   16.286034] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: 

mutt upgrade in testing broke, downgrade worked

[songbird]

2.2.3-1 version works
2.2.3-2 version does not work


  songbird

Re: file born 30 seconds after its creation on ext4 - bug?

[David Wright]

On Mon 02 May 2022 at 01:30:08 (+0200), Vincent Lefevre wrote:
> On 2022-04-30 15:19:21 +0200, Thomas Schmitt wrote:
> > An explanation of the observed problem would need:
> > - a mechanism which delayed the content production of the inode while it
> >   was already in use for open and write,
> > - or a mechanism which caused ext4 to hide the inode to other processes
> >   and to write a wrong birth timestamp,
> > - or a mechanism which deleted the file shortly after it was created and
> >   re-created it 30 seconds later with its full expected content,
> > - or something of which i cannot think yet.
> > 
> > (The birth timestamp happens to match roughly the time when the file finally
> > became visible to other processes. It matches the modification time of the
> > finally visible file.)
> 
> I'm wondering whether the data are transferred from the VFS to ext4
> necessarily within the same openat system call or could just be kept
> in the VFS as long as they are not needed elsewhere, i.e. the VFS
> behaving like a cache. In the latter case, since the VFS doesn't
> have a notion of birth timestamp (from the code I've read), a bug
> in the VFS code could explain the behavior I had observed. This is
> the only explanation I could have.

I'm not very familiar with files' birth as it's a relatively new
addition to filesystems, particularly how to display it even when
present. So I looked it up, and the ext4 wiki says it's the time
at which the inode is created. I also read in ext4 wikipedia:

  Multiblock allocator

When ext3 appends to a file, it calls the block allocator, once
for each block. Consequently, if there are multiple concurrent
writers, files can easily become fragmented on disk. However, ext4
uses delayed allocation, which allows it to buffer data and
allocate groups of blocks. Consequently, the multiblock allocator
can make better choices about allocating files contiguously on
disk. The multiblock allocator can also be used when files are
opened in O_DIRECT mode. This feature does not affect the disk
format.

So I wondered whether a delayed birth time could be caused by the
filesystem waiting a while before it actually starts creating any
allocation for the file on the disk. Having amassed some data,
depending on its size, it decides where it's going to write it,
ie which block group. Only then does it create the file's inode,
so that it can keep file contents and inode close together.

Cheers,
David.

Re: Getting a patch applied with an unresponsive maintainer

[songbird]

Adam Dinwoodie wrote:
...
> Can anyone give any advice about what my next steps might be if I want
> to get this patch made more widely available?

  in looking at the following i see there is a request for
help and that not much else has happened.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006264

also look at:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964947

  do you have access to the repository on salsa?



> I'm not a Debian developer, and as best I can tell I'd need to have
> developer privileges already to be able to kick off a non-maintainer
> upload.  And I don't think I currently have the spare bandwidth to do
> justice to becoming a developer (I'm already the maintainer of a few
> Cygwin packages, plus all of the other obligations of life...).  I am,
> however, very happy to engage with discussions about patches and
> approaches.
>
> Please keep me on the To/Cc list for any replies; I'm not currently
> subscribed to this list.

  i've tried to do that via a Cc but i'm not sure gmane honors
those.  we'll see...  :)


> Adam


  songbird

Thunderbird: cursor probleem

[Paul van der Vlis]

Hallo,

Een klant van me heeft een raar probleem, als hij e-mail beantwoord in 
Thunderbird dan is er vaak geen knipperende cursor. Hij kan wel wat 
typen, maar het is dus wat onduidelijk waar dat terecht komt.


Bij mailtjes van mij krijgt hij wel een cursor, maar ik stuur 
platte-tekst mail. Misschien dat dat het verschil maakt.


Heeft iemand een idee wat dit zou kunnen zijn?

Groet,
Paul


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

Re: mariadb does not run

[tomas]

On Mon, May 02, 2022 at 02:34:56PM +0200, Lucio Crusca wrote:
> Il 02/05/22 12:54, mick crane ha scritto:
> > I don't know anything about this but
> > https://dba.stackexchange.com/questions/184283/mariadb-10-1-galera-cluster-error
> > 
> > says The source of this error
> 
> Thanks but... it's not the same error, nor the same context.

Have you tried to start the mariadb server by hand?

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: mariadb does not run

[mick crane]

On 2022-05-02 13:34, Lucio Crusca wrote:

Il 02/05/22 12:54, mick crane ha scritto:

I don't know anything about this but
https://dba.stackexchange.com/questions/184283/mariadb-10-1-galera-cluster-error 
says The source of this error


Thanks but... it's not the same error, nor the same context.


I just searched for $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION 
(code=exited, status=1/FAILURE)
think that was the first one, there's a few others about wanting an IP 
address.


mick
--
Key ID4BFEBB31

Re: Dual boot - first time using UEFI

[Andrew M.A. Cater]

On Mon, May 02, 2022 at 12:44:32PM +0200, Hans wrote:
> Hi folks, 
> 
> yesterday I installed debian bullseye besides a windows system. As UEFI could 
> not switched off, I used gparted to make the windows partition smaller. 
> 
> Then used an usb-stick and installed bullseye as usual.
> 
> However, the installer discovered UEFI and respected this, but atthe first 
> boot, only windows could still be booted. 
> 
> But the bios allowed me, to boot into windows again (using the F12 key) , and 
> I could start the installed debian.
> 
> When I got it running, I tried to install grub again onto the MBR, which was 
> successfull. But now appeared a blue screen, with choices: "Wait 10 seconds - 
> go on - Restart - Do not ask any more" (similar, is from my remembers).
> 
> After choosing "Do not ask any more", the next reboot showed me the well 
> known 
> grub starting screen.
> 
> Well, everything is working, but the problem is: I have nothing learnt of 
> this! 
> 
> Can ssomebody explain, what technically the grub installer did do? At one 
> point it said "I have dicovered another EFI partition, shall I use it?" (or 
> similar, it is from my remembers).
> 
> Thanky for making things clear.
> 
> Best 
> 
> Hans
> 

Hello Hans,

I think this has also been covered in another thread here. 

If Windows is the _only_ system on a disk, it hijacks the UEFI booting
process slightly :)

Most people never notice this because they don't dual boot ever.

If you install Debian first, it will install entries into the EFI 
partition. If you then install Windows, it will set its own EFI entries as
first and does not recognise any other operating system. 

If you have Windows installed first and then install Debian, it _should_
run os-prober and discover that Windows is already there and set it as
an entry within grub-efi and Grub's menus.

If not, you still end up with Windows first and have to boot using a
recovery disk somehow. Rerunning the grub install process at this point
does install os-prober and then the system "just works", I think.

See also the notes to Richard Owlett about how to dual boot a Debian/
Windows system in the other thread.

With every good wish, as ever,

Andy Cater




>  
> 
> 

Re: mariadb does not run

[Lucio Crusca]

Il 02/05/22 12:54, mick crane ha scritto:

I don't know anything about this but
https://dba.stackexchange.com/questions/184283/mariadb-10-1-galera-cluster-error 


says The source of this error


Thanks but... it's not the same error, nor the same context.

Re: mariadb does not run

[mick crane]

On 2022-05-02 09:55, Lucio Crusca wrote:

Until yesterday I had mariadb 10.6 running on my system
(bookworm/sid). It was behaving strangely, so I decided to stop it,
uninstall it, remove all databases during uninstall (it's a developer
system, so no real data to save there) and install it again.

Before reinstalling it, I checked that /var/lib/mysql did not exist
anymore. I even manually removed /etc/mysql along with all the
contained files and purged dbconfig-common (just in case it matters),
then I rebooted the system and finally I installed mariadb-server with
its dependencies using aptitude. Installation went through without
errors, but it did not ask me to set a password for the mariadb root
user (maybe that's ok, I'm not sure).




Any clues?


I don't know anything about this but
https://dba.stackexchange.com/questions/184283/mariadb-10-1-galera-cluster-error
says The source of this error is due to the rsync program already in 
use, so the solution was to terminate it :


Dunno if that helps ?

mick
--
Key ID4BFEBB31

Dual boot - first time using UEFI

[Hans]

Hi folks, 

yesterday I installed debian bullseye besides a windows system. As UEFI could 
not switched off, I used gparted to make the windows partition smaller. 

Then used an usb-stick and installed bullseye as usual.

However, the installer discovered UEFI and respected this, but atthe first 
boot, only windows could still be booted. 

But the bios allowed me, to boot into windows again (using the F12 key) , and 
I could start the installed debian.

When I got it running, I tried to install grub again onto the MBR, which was 
successfull. But now appeared a blue screen, with choices: "Wait 10 seconds - 
go on - Restart - Do not ask any more" (similar, is from my remembers).

After choosing "Do not ask any more", the next reboot showed me the well known 
grub starting screen.

Well, everything is working, but the problem is: I have nothing learnt of 
this! 

Can ssomebody explain, what technically the grub installer did do? At one 
point it said "I have dicovered another EFI partition, shall I use it?" (or 
similar, it is from my remembers).

Thanky for making things clear.

Best 

Hans

 

Re: sane-backend for Epson EcoTank ET-2711

[Brian]

On Mon 02 May 2022 at 00:02:23 +0200, Dieter Rohlfing wrote:

> Am Sun, 1 May 2022 12:26:00 +0100
> schrieb Brian :
> 
> >Download the Epson (non-free) drivers.
> 
> Done. The ET-2711 is now recognized in buster and bullseye as locally
> connected scanner.
> 
> I can scan with simple-scan and 'scanimage -T' completes without any
> error. But xsane terminates with 'Segmentation fault'.

Looks like a win to me (being able to scan as aopposed to no scanning).
I cannot explain the behaviour of xsane.

The non-working epsonds backend could be reported at

  https://gitlab.com/sane-project/backends/-/issues

-- 
Brian.

Getting a patch applied with an unresponsive maintainer

[Adam Dinwoodie]

Hello!

I've found a bug in the dhcpcd5 package[0].  I've submitted a patch[1],
and I'd like to look at getting it included in the official package, not
least so I can stop maintaining my own local patches.  However -- unlike
when I've gone through this process after reporting bugs in other
packages -- the maintainer here doesn't seem to be monitoring or
responding to the BTS.

[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008059
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008059#34

Can anyone give any advice about what my next steps might be if I want
to get this patch made more widely available?

I'm not a Debian developer, and as best I can tell I'd need to have
developer privileges already to be able to kick off a non-maintainer
upload.  And I don't think I currently have the spare bandwidth to do
justice to becoming a developer (I'm already the maintainer of a few
Cygwin packages, plus all of the other obligations of life...).  I am,
however, very happy to engage with discussions about patches and
approaches.

Please keep me on the To/Cc list for any replies; I'm not currently
subscribed to this list.

Adam

mariadb does not run

[Lucio Crusca]

Until yesterday I had mariadb 10.6 running on my system (bookworm/sid). 
It was behaving strangely, so I decided to stop it, uninstall it, remove 
all databases during uninstall (it's a developer system, so no real data 
to save there) and install it again.


Before reinstalling it, I checked that /var/lib/mysql did not exist 
anymore. I even manually removed /etc/mysql along with all the contained 
files and purged dbconfig-common (just in case it matters), then I 
rebooted the system and finally I installed mariadb-server with its 
dependencies using aptitude. Installation went through without errors, 
but it did not ask me to set a password for the mariadb root user (maybe 
that's ok, I'm not sure).


However now mariadb does not run anymore, complaining with:

# systemctl status mariadb
× mariadb.service - MariaDB 10.6.7 database server
 Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; 
vendor preset: enabled)
 Active: failed (Result: exit-code) since Mon 2022-05-02 10:45:24 
CEST; 8min ago

   Docs: man:mariadbd(8)
 https://mariadb.com/kb/en/library/systemd/
Process: 4879 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root 
-d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 4880 ExecStartPre=/bin/sh -c systemctl unset-environment 
_WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 4882 ExecStartPre=/bin/sh -c [ ! -e 
/usr/bin/galera_recovery ] && VAR= ||   VAR=`cd /usr/bin/..; 
/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment 
_WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 4890 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS 
$_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)

   Main PID: 4890 (code=exited, status=1/FAILURE)
 Status: "MariaDB server is down"
CPU: 136ms

mag 02 10:45:24 t470 mariadbd[4890]: 2022-05-02 10:45:24 0 [ERROR] Could 
not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some 
plugins may be not loaded
mag 02 10:45:24 t470 mariadbd[4890]: 2022-05-02 10:45:24 0 [ERROR] Can't 
open and lock privilege tables: Table 'mysql.servers' doesn't exist
mag 02 10:45:24 t470 mariadbd[4890]: 2022-05-02 10:45:24 0 [Note] Server 
socket created on IP: '0.0.0.0'.
mag 02 10:45:24 t470 mariadbd[4890]: 2022-05-02 10:45:24 0 [Note] Server 
socket created on IP: '::'.
mag 02 10:45:24 t470 mariadbd[4890]: 2022-05-02 10:45:24 0 [ERROR] Fatal 
error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist

mag 02 10:45:24 t470 mariadbd[4890]: 2022-05-02 10:45:24 0 [ERROR] Aborting
mag 02 10:45:24 t470 mariadbd[4890]: Warning: Memory not freed: 280
mag 02 10:45:24 t470 systemd[1]: mariadb.service: Main process exited, 
code=exited, status=1/FAILURE
mag 02 10:45:24 t470 systemd[1]: mariadb.service: Failed with result 
'exit-code'.
mag 02 10:45:24 t470 systemd[1]: Failed to start MariaDB 10.6.7 database 
server.


Any clues?

Re: I Simply Cannot Install Tor Browser in my Chromebook

[didier gaumet]

Le lundi 02 mai 2022 à 03:41 -0400, Terron Hampton a écrit :
> Hello. I have spent hours the past week trying anything I can to
> install Tor Browser to no avail. I've read all of the how-to guides
> with detailed commands, etc. and nothing works for installing Tor
> Browser in Debian Bullseye 11. I have the Tor Browser downloaded
> file, but I cannot seem to make it visible to linux. I've looked and
> looked around and nothing. Is there any way I can live chat with
> someone and try some of the tricks and can get good commands for
> installation and hopefully get great results? Please, please help me.
> 
> Sincerely 
> 
> Terron

Hello,

(I don't use Tor)

For the upstream version of tor you downloaded from the Tor website, there does 
not seem to be en entry generated in the application menu of  some desktop 
environments (Gnome and possibly others).

For a better integration, the favored way of installing applications in Linux 
is to use a package manager or a Linux app store, not to download and install 
an application from its upstream editor. Tor is packaged by Debian.

There is a page of the Debian wiki detailing Tor usage and its installation:
https://wiki.debian.org/TorBrowser

Re: I Simply Cannot Install Tor Browser in my Chromebook

[tomas]

On Mon, May 02, 2022 at 03:41:46AM -0400, Terron Hampton wrote:
> Hello. I have spent hours the past week trying anything I can to install
> Tor Browser to no avail. I've read all of the how-to guides with detailed
> commands, etc. and nothing works for installing Tor Browser in Debian
> Bullseye 11. I have the Tor Browser downloaded file, but I cannot seem to
> make it visible to linux. I've looked and looked around and nothing. Is
> there any way I can live chat with someone and try some of the tricks and
> can get good commands for installation and hopefully get great results?
> Please, please help me.

There is a package named torbrowser-launcher which helps you downloading
and installing the Tor browser. I'd recommend giving it a try.

If you want to do the install yourself, you'll have to provided more
details on what you have tried:

 - where did you get the package from?
 - what's the package file name?
 - what do you mean by "visible to linux" (we don't see
   what you see ;-)

Probably a couple of other things.

Cheers
-- 
t


signature.asc
Description: PGP signature

I Simply Cannot Install Tor Browser in my Chromebook

[Terron Hampton]

Hello. I have spent hours the past week trying anything I can to install
Tor Browser to no avail. I've read all of the how-to guides with detailed
commands, etc. and nothing works for installing Tor Browser in Debian
Bullseye 11. I have the Tor Browser downloaded file, but I cannot seem to
make it visible to linux. I've looked and looked around and nothing. Is
there any way I can live chat with someone and try some of the tricks and
can get good commands for installation and hopefully get great results?
Please, please help me.

Sincerely

Terron

Re: sane-backend for Epson EcoTank ET-2711

[didier gaumet]

Le lundi 02 mai 2022 à 00:02 +0200, Dieter Rohlfing a écrit :

[...]
> So long story short: network scaning does not work with the Epson
> drivers. :-(

Hello,

It seems there is a specific network plugin to installa and configure
(look at 6.1 and 7 chapters)
http://download.ebz.epson.net/man/linux/imagescanv3_e.html#sec1