Lxde keyboard

[Gunnar Gervin]

Hi.
@ disappeared in Debian Buster
Lxde+Debian Desktop Environm.
In Xfce it was ok, & now I saw th harddisk(so it's ok).I probly took wrong
font. Trying nn_NO.UTF-8
& LXDE. Change & Challenge=ok
BR,
geg

Re: Strange email behaviour................

[Charlie]

On Tue, 20 Jul 2021 17:51:59 -0400 rhkra...@gmail.com Informed
me about Re: Strange email behaviour

> Oops, disregard my answer / comments above, they are misleading / not
> on point -- I didn't read the original post carefully enough.

Thank you all for your input. It is valued and has alleviated
my concerns.

Charlie

-- 
Registered Linux User:- 329524

***

Consciousness is in the first place not a matter of "I think"
but of "I can." --Maurice Merleau-Ponty

***
Debian GNU/Linux - Magic indeed.

-

Suggestion

[Gunnar Gervin]

Hi guys and girls.
I can probly manage without Gparted cos good man cfdisk
But others really need it 2 often.
In 'Manage flags' put a Root flag
So the partition newbies can set Root a specified place, usually in main
partition. Now u cannot flag more than 2 flags, like Boot and lvm (to
cfdisk partition sda) or boot and esp(to tell it's uefi).
But if Root's added as an option, we could flag Root and Boot in that 1t
(biggest) sda1, add sda2 for backup and restore, & sda3; Virtual memory
expanse (swap).

Cos Debian (also) whined about Root system setting. But Never came up with
any solution How.
Which Bullseye maybe did(?).
BR
geg

Re: Boring Buster => Bullseye Upgrade Report

[Erwan David]

Le 22/07/2021 à 21:03, Polyna-Maude Racicot-Summerside a écrit :
> Hi,
>
> On 2021-07-22 2:16 p.m., Georgi Naplatanov wrote:
>> On 7/22/21 8:48 PM, Dan Ritter wrote:
>>> I upgraded a Gigabyte NUC-style tiny desktop (i5-5010U) from
>>> buster to bullseye. Nothing interesting to report; it just
>>> worked.
>>>
>> +1
>>
>> I did it on the beginning of May and I have had no problems so far.
>>
>> Docker provides packages for Debian 11. A problem was VirtualBox but I
>> installed packages for Ubunto as I did when Debain 10 was still testing.
>>
> I simply compiled the package made for Ubuntu from source on my Debian
> Buster/Bullseye. It worked out of the box, later I modified some options
> (don't remember which one).
>
> I often did so for package that weren't present in Debian.
> Rarely had to do some modifications.
For virtualbox, I use the pacakge from sid, works without any problem on
bullseye

Re: Root & Boot Trouble

[Gunnar Gervin]

But I liked your 'quarrel' and the funny stories.
geg

On Thu, 22 Jul 2021 at 19:02, Gunnar Gervin  wrote:

> I seem to sort it out (or done already in Gparted "Clearing" format to
> remove old rubbish)
> & then -probably- using LVM to set it up correctly using terminal instead
> of GUI.
> Maybe I'll test Bullseye later, cos Debian Buster is the worst distro I
> ever tried, Windows included..
>
> On Thu, 22 Jul 2021 at 11:10, Greg Wooledge  wrote:
>
>> On Thu, Jul 22, 2021 at 12:36:53PM +0300, Gunnar Gervin wrote:
>> > Description of happenings when I tried to install LMDE4 after I had
>> Debian
>>
>> I had to Google this to see what it *is*.  Google says,
>>
>>  Download LMDE 4 Debbie. Information. LMDE is a Linux Mint project which
>>  stands for "Linux Mint Debian Edition".
>>
>> So, LMDE (version 4 or whatever) is an entirely separate operating system.
>> It's not something you install on top of Debian.  It's something you
>> install *instead* of Debian.
>>
>> If you want to remove Debian and replace it with LMDE, and if the LMDE
>> installer isn't working correctly for you, then you will need to contact
>> an LMDE mailing list instead of debian-user.  We simply do not know how
>> LMDE's installer works.
>>
>>

Re: Boring Buster => Bullseye Upgrade Report

[Polyna-Maude Racicot-Summerside]

Hi,

On 2021-07-22 2:16 p.m., Georgi Naplatanov wrote:
> On 7/22/21 8:48 PM, Dan Ritter wrote:
>>
>> I upgraded a Gigabyte NUC-style tiny desktop (i5-5010U) from
>> buster to bullseye. Nothing interesting to report; it just
>> worked.
>>
> 
> +1
> 
> I did it on the beginning of May and I have had no problems so far.
> 
> Docker provides packages for Debian 11. A problem was VirtualBox but I
> installed packages for Ubunto as I did when Debain 10 was still testing.
> 
I simply compiled the package made for Ubuntu from source on my Debian
Buster/Bullseye. It worked out of the box, later I modified some options
(don't remember which one).

I often did so for package that weren't present in Debian.
Rarely had to do some modifications.
> Kind regards
> Georgi
> 

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Re: Root & Boot Trouble

[Gunnar Gervin]

I seem to sort it out (or done already in Gparted "Clearing" format to
remove old rubbish)
& then -probably- using LVM to set it up correctly using terminal instead
of GUI.
Maybe I'll test Bullseye later, cos Debian Buster is the worst distro I
ever tried, Windows included..

On Thu, 22 Jul 2021 at 11:10, Greg Wooledge  wrote:

> On Thu, Jul 22, 2021 at 12:36:53PM +0300, Gunnar Gervin wrote:
> > Description of happenings when I tried to install LMDE4 after I had
> Debian
>
> I had to Google this to see what it *is*.  Google says,
>
>  Download LMDE 4 Debbie. Information. LMDE is a Linux Mint project which
>  stands for "Linux Mint Debian Edition".
>
> So, LMDE (version 4 or whatever) is an entirely separate operating system.
> It's not something you install on top of Debian.  It's something you
> install *instead* of Debian.
>
> If you want to remove Debian and replace it with LMDE, and if the LMDE
> installer isn't working correctly for you, then you will need to contact
> an LMDE mailing list instead of debian-user.  We simply do not know how
> LMDE's installer works.
>
>

Re: Boring Buster => Bullseye Upgrade Report

[Georgi Naplatanov]

On 7/22/21 8:48 PM, Dan Ritter wrote:
> 
> I upgraded a Gigabyte NUC-style tiny desktop (i5-5010U) from
> buster to bullseye. Nothing interesting to report; it just
> worked.
> 

+1

I did it on the beginning of May and I have had no problems so far.

Docker provides packages for Debian 11. A problem was VirtualBox but I
installed packages for Ubunto as I did when Debain 10 was still testing.

Kind regards
Georgi

Re: Boring Buster => Bullseye Upgrade Report

[Felix Miata]

Dan Ritter composed on 2021-07-22 13:48 (UTC-0400):

> I upgraded a Gigabyte NUC-style tiny desktop (i5-5010U) from
> buster to bullseye. Nothing interesting to report; it just
> worked.


I did same last night, online, on an old 32 bit P4, which likewise just worked.
-- 
Evolution as taught in public schools is, like religion,
based on faith, not based on science.

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

Felix Miata

Boring Buster => Bullseye Upgrade Report

[Dan Ritter]

I upgraded a Gigabyte NUC-style tiny desktop (i5-5010U) from
buster to bullseye. Nothing interesting to report; it just
worked.

Re: USB audio device no longer showing up

[Tom Yates]

On Thu, 22 Jul 2021, Thomas Amm wrote:


according to my long and sometimes painful experience with USB-audio
interfaces I suspect that it is the internal USB connector in your
external interface that's failing. So hardware problem, indeed.
These connectors are 50¢ apiece, but unfortunately they are usually SMC
parts soldered directy on the print circuit board so they provide very
little resistance against the shearing tension implied by the USB
cable. I've just luckily been able to repair a € 500.- desktop
synthesizer from exactly that kind of damage.


i note in passing this is another great use for USB hubs.  recently when i 
started having serious video camera problems, and having diagnosed a USB 
socket on its way out, i ended up replacing a £20 hub with another £20 
hub, instead of having to try, as you say, to repair a multi-hundred-euro 
motherboard.


use a cheap hub for all your day-to-day connection and disconnection 
needs, and save wear and tear on your fragile motherboard connectors.




--

  Tom Yates  -  https://www.teaparty.net

Re: kernel patch for "FULL FREEZE" branch /testing

[Tixy]

On Thu, 2021-07-22 at 16:00 +0200, Marco Möller wrote:
> So, although it is full freeze time, the former kernel with all its 
> already known and tested functionality will not be specially patched, 
> but the new kernel is taken although it besides containing the patch 
> might also bring changed functionality?
> Simply asking for curiosity, not that it would be of further importance 
> for me.

I have no inside knowledge, but I would speculate that the release team
accept 'extra' package changes if they would normally be part of how
the security team issues fixes for that package in a stable release. 

For highly complex software like the Linux kernel, and web browsers
like Firefox, Debian security releases tend to stick with upstream long
-term-support releases that contain the security fix. It's completely
impractical to maintain a Debian specific fork and patch that.

-- 
Tixy

Re: kernel patch for "FULL FREEZE" branch /testing

[Andrew M.A. Cater]

On Thu, Jul 22, 2021 at 04:00:26PM +0200, Marco Möller wrote:
> On 22.07.21 13:49, Tixy wrote:
> > On Thu, 2021-07-22 at 12:23 +0200, Marco Möller wrote:
> > > Hello everyone! The Debian development branch "bullseye"(/testing) is in
> > > status "full freeze", if I am correctly informed, and packages from
> > > /unstable are for quite some time already no more automatically moved
> > > from /unstable to /testing.
> > > Do you know how Debian handles situations like the current
> > > CVE-2021-33909 patched kernel being already in /unstable but for sure
> > > also /testing, the soon /stable, would benefit from receiving the patch
> > > as provided in 5.10.46-2 ?
> > > The patched version I am speaking about is this:
> > > linux-image-5.10.0-8-amd64/unstable 5.10.46-2 amd64
> > > In my "bullseye" installation, which I update daily, I still have
> > > linux-image-5.10.0-7-amd64/testing,now 5.10.40-1 amd64
> > 
> > 5.10.46-2 is now in testing, I've just updated to it.
> > 
> > Presumably the process is as described in full freeze announcement,
> > i.e. package developer makes unblock request to allow migration into
> > testing and release team grant it if they think it meets the criteria
> > for release.
> > 
> 
> It meanwhile arrived also in the mirror which I am using. Nice.
> 
> So, although it is full freeze time, the former kernel with all its already
> known and tested functionality will not be specially patched, but the new
> kernel is taken although it besides containing the patch might also bring
> changed functionality?
> Simply asking for curiosity, not that it would be of further importance for
> me.
> 

That's how it works. Normally, unstable -> testing would just migrate. Security 
fixes to stable would be made in the normal course of events. 

Bullseye / Debian 11 is now in really hard freeze - ready for release very 
shortly. So security fixes are more or less the only things going in.
Each of them is hand approved so as not to break everything else. The very 
latest kernel/systemd security update is a big deal - so it got
hand approved very quickly.

In general, any bug fixed package overrides all the files of the previous 
package: if there's a package foo-1.0.0 and foo1.0.1 is a security fix,
foo1.0.1 wll replace all the previous files from foo1.0.0. There are 
exceptions, especially where there are modified configuration files: in that
case, there will normally be a question asked sa to whether to update the files 
or not. In some cases, the new package will leave a sample config 
file (with a dpkg.new extension, I think) in the correct place to be looked at 
and edited as necessary.

All the very best, as ever,

Andy Cater 

Re: kernel patch for "FULL FREEZE" branch /testing

[Marco Möller]

On 22.07.21 13:49, Tixy wrote:

On Thu, 2021-07-22 at 12:23 +0200, Marco Möller wrote:

Hello everyone! The Debian development branch "bullseye"(/testing) is in
status "full freeze", if I am correctly informed, and packages from
/unstable are for quite some time already no more automatically moved
from /unstable to /testing.
Do you know how Debian handles situations like the current
CVE-2021-33909 patched kernel being already in /unstable but for sure
also /testing, the soon /stable, would benefit from receiving the patch
as provided in 5.10.46-2 ?
The patched version I am speaking about is this:
linux-image-5.10.0-8-amd64/unstable 5.10.46-2 amd64
In my "bullseye" installation, which I update daily, I still have
linux-image-5.10.0-7-amd64/testing,now 5.10.40-1 amd64


5.10.46-2 is now in testing, I've just updated to it.

Presumably the process is as described in full freeze announcement,
i.e. package developer makes unblock request to allow migration into
testing and release team grant it if they think it meets the criteria
for release.



It meanwhile arrived also in the mirror which I am using. Nice.

So, although it is full freeze time, the former kernel with all its 
already known and tested functionality will not be specially patched, 
but the new kernel is taken although it besides containing the patch 
might also bring changed functionality?
Simply asking for curiosity, not that it would be of further importance 
for me.

Re: kernel patch for "FULL FREEZE" branch /testing

[Tixy]

On Thu, 2021-07-22 at 12:23 +0200, Marco Möller wrote:
> Hello everyone! The Debian development branch "bullseye"(/testing) is in 
> status "full freeze", if I am correctly informed, and packages from 
> /unstable are for quite some time already no more automatically moved 
> from /unstable to /testing.
> Do you know how Debian handles situations like the current 
> CVE-2021-33909 patched kernel being already in /unstable but for sure 
> also /testing, the soon /stable, would benefit from receiving the patch 
> as provided in 5.10.46-2 ?
> The patched version I am speaking about is this:
> linux-image-5.10.0-8-amd64/unstable 5.10.46-2 amd64
> In my "bullseye" installation, which I update daily, I still have
> linux-image-5.10.0-7-amd64/testing,now 5.10.40-1 amd64

5.10.46-2 is now in testing, I've just updated to it.

Presumably the process is as described in full freeze announcement,
i.e. package developer makes unblock request to allow migration into
testing and release team grant it if they think it meets the criteria
for release.

-- 
Tixy

Re: Root & Boot Trouble

[Greg Wooledge]

On Thu, Jul 22, 2021 at 12:36:53PM +0300, Gunnar Gervin wrote:
> Description of happenings when I tried to install LMDE4 after I had Debian

I had to Google this to see what it *is*.  Google says,

 Download LMDE 4 Debbie. Information. LMDE is a Linux Mint project which
 stands for "Linux Mint Debian Edition".

So, LMDE (version 4 or whatever) is an entirely separate operating system.
It's not something you install on top of Debian.  It's something you
install *instead* of Debian.

If you want to remove Debian and replace it with LMDE, and if the LMDE
installer isn't working correctly for you, then you will need to contact
an LMDE mailing list instead of debian-user.  We simply do not know how
LMDE's installer works.

Re: USB audio device no longer showing up

[Thomas Amm]

On Tue, 2021-07-20 at 11:26 +, Dr. Jennifer Nussbaum wrote:
> I've been using a Schiit Modi 3 D/A converter for my main desktop
> audio for a year or two. In the last week, it's been sporadically
> vanishing from PulseAudio.
> 
> It's normally plugged into a USB port on my monitor, which has
> several such ports, all of which work with other devices. When I plug
> it in, dmesg shows me:
> 
> [2126764.183346] usb 3-3.4: new full-speed USB device number 75 using
> xhci_hcd
> [2126765.035388] usb 3-3-port4: Cannot enable. Maybe the USB cable is
> bad?
> [2126765.887389] usb 3-3-port4: Cannot enable. Maybe the USB cable is
> bad?
> [2126765.887461] usb 3-3-port4: attempt power cycle
> [2126768.319399] usb 3-3-port4: Cannot enable. Maybe the USB cable is
> bad?
> [2126769.171424] usb 3-3-port4: Cannot enable. Maybe the USB cable is
> bad?
> [2126769.171483] usb 3-3-port4: unable to enumerate USB device
> 
> I get similar messages from other ports; other devices show up fine.
> This port is successfully providing power to the Schiit.
> 
> Though "Maybe the USB cable is bad?" is a dubious-sounding message, I
> did swap out the existing random cable with a brand-new good-quality
> one, with no difference.
> 
> I also tried to plug the Schiit into a Debian laptop, with the same
> results as above. Confoundingly, after this test, I re-plugged it
> into my monitor and it magically started to work -- it showed up in
> dmesg, it started to play audio.
> 
> However, hoping it magically works isn't a good long-term solution.
> Is there any way to figure out what's causing this? Could it be a
> hardware problem with the Schiit? If so, how do I report it to them?
> 
> 
Hi,

according to my long and sometimes painful experience with USB-audio
interfaces I suspect that it is the internal USB connector in your
external interface that's failing. So hardware problem, indeed.
These connectors are 50¢ apiece, but unfortunately they are usually SMC
parts soldered directy on the print circuit board so they provide very
little resistance against the shearing tension implied by the USB
cable. I've just luckily been able to repair a € 500.- desktop
synthesizer from exactly that kind of damage. That was hard enough
despite the usage of a full-size connector on the extarnal side and
probably much more space to work than inside a portable audio
interface.
I've seen this kind of damage a lot in USB interfaces and usually
there's little hope of repair unless you put a lot of time and skill in
it.

kernel patch for "FULL FREEZE" branch /testing

[Marco Möller]

Hello everyone! The Debian development branch "bullseye"(/testing) is in 
status "full freeze", if I am correctly informed, and packages from 
/unstable are for quite some time already no more automatically moved 
from /unstable to /testing.
Do you know how Debian handles situations like the current 
CVE-2021-33909 patched kernel being already in /unstable but for sure 
also /testing, the soon /stable, would benefit from receiving the patch 
as provided in 5.10.46-2 ?

The patched version I am speaking about is this:
linux-image-5.10.0-8-amd64/unstable 5.10.46-2 amd64
In my "bullseye" installation, which I update daily, I still have
linux-image-5.10.0-7-amd64/testing,now 5.10.40-1 amd64
Best wishes, Marco.

Re: where can i find a list of wireless adapter that debian support

[loushanguan2015]

Thank Gene, i'd better give up search for ideal wireless  adapter
my old pci wireless adapter needn't non-free firmware, but new adapter need, as 
Andrew has said 

Re: Root & Boot Trouble

[Gunnar Gervin]

Hi again.
I wrote fail word:
"It said Root is placed so far away"
"It said BOOT is placed so far away"

On Thu, 22 Jul 2021 at 12:36, Gunnar Gervin  wrote:

> Hello all.
> In bottom of this email is the Boot Repair Report in /etc/fstab.
>
> Description of happenings when I tried to install LMDE4 after I had Debian
> i386 32bit Buster (only) on my old Macbook from 2007:
> 1. Burned an ISO image of lmde4 4.19 (4,8GB) on a dvd.
> 2. Pressed option key & pressed Power on button, dvd image came up,
> pressed it.
> 3. At the end of the installation process, I was told to put Root in a
> partition of minimum 30GB.
> I pressed on Boot Repair, it was a program in Cinnamon. The Boot repair
> claimed that the Boot system was placed far from the start of the sda
> (harddisk); that the boot installer might not see it. It said that if
> it wouldn't mount hda it might not know where to mount it.
> I opened "Disks", it looked like Gnome Disk Utility when I opened it.
> Opened "Modify Flags" in "Disks", hatched "Boot" and "esp" on sda.
> Tried mount hda2 (it suggested mnt/hda2). (Should I've used Default
> instead?
> But it seemed not to give the correct option).
> Made a partition of 30GB at start (left side), called hda1, hatched Boot &
> Esp.
> Looked for "Root" in Flags. Saw Bios-grub option in Flags but it
> disappeared, never saw it again. Tried find help in Linux Mint but their
> communication system had become more difficult, or the machine couldn't
> cope in "live" mode only, I was too tired, &/or it was a typo in the
> "Nickserv" instruction they gave me.
> Sent a help email to Boot Repair email, but no answer yet. Please help.
> Like I said before, this culture of tech is mostly internal; basic
> knowledge, talent, or telepathy seem required, as well as dedication,
> energy & time in abundance.
> BR,
> geg.
> PS
> to boot.repair
> At the end of the partitioning (, after I did my best -whatever that is-
> to mount
> sda1 in Gnome Disk Utility), I couldn't see any way to e.g. Flag Root
> (hint- hint) in Gparted, or partition Root to anything close to the
> Installing program's satisfaction.
> Attached is the Boot Repair program's report of what's wrong. It said Root
> is placed so far away from the start of sda(hdd) that the Installer may not
> see it(?).
> I give up; I'm in way over my head.
> Best regards,
>
> # UNCONFIGURED FSTAB FOR BASE SYSTEM
>
> overlay / overlay rw 0 0
>
> tmpfs /tmp tmpfs nosuid,nodev 0 0
>
> /dev/sda1 /mnt/sda1 EXT2 nosuid,nodev,nofail,x-gvfs-show 0 0
>
> /dev/sda3 /mnt/sda3 EXT2
> nosuid,nodev,nofail,x-gvfs-show,noauto,x-udisks-auth 0 0
>
> /dev/sda2 none swap sw,x-udisks-auth,noauto 0 0
>

Root & Boot Trouble

[Gunnar Gervin]

Hello all.
In bottom of this email is the Boot Repair Report in /etc/fstab.

Description of happenings when I tried to install LMDE4 after I had Debian
i386 32bit Buster (only) on my old Macbook from 2007:
1. Burned an ISO image of lmde4 4.19 (4,8GB) on a dvd.
2. Pressed option key & pressed Power on button, dvd image came up, pressed
it.
3. At the end of the installation process, I was told to put Root in a
partition of minimum 30GB.
I pressed on Boot Repair, it was a program in Cinnamon. The Boot repair
claimed that the Boot system was placed far from the start of the sda
(harddisk); that the boot installer might not see it. It said that if
it wouldn't mount hda it might not know where to mount it.
I opened "Disks", it looked like Gnome Disk Utility when I opened it.
Opened "Modify Flags" in "Disks", hatched "Boot" and "esp" on sda.
Tried mount hda2 (it suggested mnt/hda2). (Should I've used Default instead?
But it seemed not to give the correct option).
Made a partition of 30GB at start (left side), called hda1, hatched Boot &
Esp.
Looked for "Root" in Flags. Saw Bios-grub option in Flags but it
disappeared, never saw it again. Tried find help in Linux Mint but their
communication system had become more difficult, or the machine couldn't
cope in "live" mode only, I was too tired, &/or it was a typo in the
"Nickserv" instruction they gave me.
Sent a help email to Boot Repair email, but no answer yet. Please help.
Like I said before, this culture of tech is mostly internal; basic
knowledge, talent, or telepathy seem required, as well as dedication,
energy & time in abundance.
BR,
geg.
PS
to boot.repair
At the end of the partitioning (, after I did my best -whatever that is- to
mount
sda1 in Gnome Disk Utility), I couldn't see any way to e.g. Flag Root
(hint- hint) in Gparted, or partition Root to anything close to the
Installing program's satisfaction.
Attached is the Boot Repair program's report of what's wrong. It said Root
is placed so far away from the start of sda(hdd) that the Installer may not
see it(?).
I give up; I'm in way over my head.
Best regards,

# UNCONFIGURED FSTAB FOR BASE SYSTEM

overlay / overlay rw 0 0

tmpfs /tmp tmpfs nosuid,nodev 0 0

/dev/sda1 /mnt/sda1 EXT2 nosuid,nodev,nofail,x-gvfs-show 0 0

/dev/sda3 /mnt/sda3 EXT2
nosuid,nodev,nofail,x-gvfs-show,noauto,x-udisks-auth 0 0

/dev/sda2 none swap sw,x-udisks-auth,noauto 0 0

Re: where can i find a list of wireless adapter that debian support

[Gene Heskett]

On Thursday 22 July 2021 00:58:23 loushanguan2...@sina.com wrote:

> Thank Georgi!
> the tricky part of my search for ideal adapter(needn't non-free
> firmware) isthat many vendors claim they support linux, but i'm afraid
> they require non-free firmware is there some easy way to find out if
> it requires non-free firmware?

I'll repeat why you will find there is a 100% need for sealed blobs of 
firmware. Because the FCC requires that the frequencies used be limited 
to the assigned band for this service, and the power outputs are also 
limited, these are options for software radios, must be enforced with 
with code whose limits are not accessable to the user. So all code that 
manages this, is by the rules, sealed code, and the radio doesn't work 
w/o it.

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