from:"pham...@bluewin.ch"

Hello,
I followed your instructions though from the mar. 11 juin 2024 (on bug #1072687 
that you closed which forced me to reopen the current bug) ?? Not ??
Please enable trace logging in NetworkManager.
The dmesg doesn't show anything unusual at the first view.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/introduction-to-networkmanager-debugging_configuring-and-managing-networking#temporarily-setting-log-levels-at-run-time-using-nmcli_introduction-to-networkmanager-debugging
nmcli general logging level TRACE domains ALL
Then use 
journalctl -u NetworkManager -b
Already on 06.06.2024 you ask me (on bug #1072687 that you closed which forced 
me to reopen the current bug) :
Run dmesg when networking isn't successful and show the output.
and then you told me that it was not the right line command to make ??
2 times you provided me with orders to perform to provide you with more details.
2 times I provided you with the requested data ??
What else do you want ? Please provide me with the commands to execute very 
clearly and or the names and locations of the desired log files.
Regards.

Bug#1074303: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

I have executed the command you asked me for following the protocol you also 
asked me for!!
If you want something else, ask me again with all the details necessary for its 
execution.
I am willing to help you solve bugs under Debian but you have to put your own 
effort into it too and tell me what I have to do to help you...
This is the second time you've asked me to provide you with logs and twice 
after providing them you tell me that it's not working ?!? 
Greetings.
Message d'origine
De : bi...@debian.org
Date : 16/07/2024 - 12:03 (E)
À : pham...@bluewin.ch, 1074...@bugs.debian.org, m...@dorfdsl.de
Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when 
booting Debian
Am 16.07.24 um 11:59 schrieb pham...@bluewin.ch: > Hello, > > > I followed your 
instructions though from the mar. 11 juin 2024 (on bug > #1072687 that you 
closed which forced me to reopen the current bug) ?? > Not ?? I asked for a 
debug/trace log showing the problem. your log only contains messages of INFO 
and above and do not show any problem.

Bug#1074303: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

I apologize but I don't speak German.

Now you want me to run the command :

nmcli general logging

That's it ??

I hope that after this you will not tell me a third time that I did not provide 
you with the correct logs... It's getting a bit tiring after a while.

Regards.


Message d'origine
De : m...@dorfdsl.de
Date : 16/07/2024 - 12:04 (E)
À : pham...@bluewin.ch
Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when 
booting Debian

Am 16.07.2024 um 11:59:35 Uhr schrieb pham...@bluewin.ch:

Zeige bitte die Ausgabe von

nmcli general logging

Da muss DEBUG für alles drinstehen.

-- 
Gruß
Marco

Bug#1074303: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

root@station:~# nmcli general logging
LEVEL  DOMAINS  

 
INFO   
PLATFORM,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,AGENTS,SETTINGS,SUSPEND,CORE,DEVICE,OLPC,INFINIBAND,FIREWALL,ADSL,BOND,VLAN,BRIDGE,TEAM,CONCHECK,DCB,DISPATCH,AUDIT,SYSTEMD,PROXY
 


Message d'origine
De : m...@dorfdsl.de
Date : 16/07/2024 - 12:21 (E)
À : pham...@bluewin.ch
Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when 
booting Debian

Am 16.07.2024 um 12:15:13 Uhr schrieb pham...@bluewin.ch:

> I have executed the command you asked me for following the protocol
> you also asked me for!!

Please also post the output. The command 'nmcli general logging' just
shows the debug levels. This is needed now to check if the change of te
debug level actually worked.


-- 
Gruß
Marco

Bug#1074303: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

This is almost the same order you asked me to do last time...

nmcli general logging level TRACE domains ALL
 
versus

nmcli general logging level LEVEL domains ALL

Are you sure from you ?

If I send you more a new logs and you tell me again that it's not what you 
need, I won't start trying to help you solve your bugs a 4th time !!!



Message d'origine
De : m...@dorfdsl.de
Date : 16/07/2024 - 12:30 (E)
À : pham...@bluewin.ch
Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when 
booting Debian

Am 16.07.2024 um 12:26:55 Uhr schrieb pham...@bluewin.ch:

> root@station:~# nmcli general logging
> LEVEL  DOMAINS
> INFO
> PLATFORM,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,AGENTS,SETTINGS,SUSPEND,CORE,DEVICE,OLPC,INFINIBAND,FIREWALL,ADSL,BOND,VLAN,BRIDGE,TEAM,CONCHECK,DCB,DISPATCH,AUDIT,SYSTEMD,PROXY
>  

That means debug level is still INFO.
Please try 
sudo nmcli general logging level LEVEL domains ALL

And show the output of the outcome. This is always important because
people on the other side need to know if the command was successful.

-- 
Gruß
Marco

Bug#1074303: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

2024-07-18 Thread pham...@bluewin.ch

Hello,
The command line you asked me to enter is invalid ?!?!
sudo nmcli general logging level LEVEL domains ALL
root@station:~# nmcli general logging level LEVEL domains ALL
Erreur : accès refusé pour définir la journalisation : Niveau de journalisation 
« LEVEL » inconnu
This is the third time you've asked me to do a job that ultimately serves no 
purpose or doesn't work !?
On top of that you closed my previous bug for no reason and I had to reopen it.
Forgive me for being blunt, but what's the problem? You don't have time to deal 
with it? If that's it, there are other maintainers who are most certainly ready 
to take over, don't you think? I just feel like I'm wasting my time with not 
motivated people ;-(
Regards.

Bug#1074303: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

2024-07-23 Thread pham...@bluewin.ch

root@station:~# nmcli general logging level DEBUG domains all
root@station:~# nmcli general logging
LEVEL  DOMAINS  


  
DEBUG  
PLATFORM,RFKILL,ETHER,WIFI,BT,MB,DHCP4,DHCP6,PPP,WIFI_SCAN,IP4,IP6,AUTOIP4,DNS,VPN,SHARING,SUPPLICANT,AGENTS,SETTINGS,SUSPEND,CORE,DEVICE,OLPC,INFINIBAND,FIREWALL,ADSL,BOND,VLAN,BRIDGE,DBUS_PROPS,TEAM,CONCHECK,DCB,DISPATCH,AUDIT,SYSTEMD,VPN_PLUGIN:INFO,PROXY
 

I will contact you as soon as the outage occurs again to provide you with the 
log.

Greetings.

Message d'origine
De : m...@dorfdsl.de
Date : 18/07/2024 - 21:34 (E)
À : pham...@bluewin.ch, 1074...@bugs.debian.org
Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when 
booting Debian

Am 18.07.2024 um 18:30:44 Uhr schrieb pham...@bluewin.ch:

> The command line you asked me to enter is invalid ?!?!
> sudo nmcli general logging level LEVEL domains ALL

LEVEL must be replaced by the level, e.g. INFO or DEBUG.

sudo nmcli general logging level DEBUG domains all

After that please check if the change has been applied:

sudo nmcli general logging

This must show DEBUG for all domains. If not, no debug logs will be
produced.

If that is the case, help can continue.

> On top of that you closed my previous bug for no reason and I had to
> reopen it.

This wasn't me.

> Forgive me for being blunt, but what's the problem? You
> don't have time to deal with it? If that's it, there are other
> maintainers who are most certainly ready to take over, don't you
> think?

I can understand that you are annoyed, but unless your system produces
DEBUG logs, nobody can further investigate that.

-- 
kind regards
Marco

Bug#1074303: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

2024-08-06 Thread pham...@bluewin.ch

I hope that this time you have the necessary information to work on this 
problem.
Greetings
root@station:~# journalctl -u NetworkManager -b
aoû 06 09:52:19 station systemd[1]: Starting NetworkManager.service - Network 
Manager...
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6364] 
NetworkManager (version 1.42.4) is starting... 
(boot:c0eea501-7070-429d-843e-b732f3d39eaf)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6365] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
aoû 06 09:52:19 station systemd[1]: Started NetworkManager.service - Network 
Manager.
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6377] 
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6414] 
manager[0x556ea1cd8000]: monitoring kernel firmware directory '/lib/firmware'.
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6415] 
monitoring ifupdown state file '/run/network/ifstate'.
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6432] 
hostname: hostname: using hostnamed
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6432] 
hostname: static hostname changed from (none) to "station"
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6434] 
dns-mgr: init: dns=default,systemd-resolved rc-manager=symlink (auto)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6443] 
rfkill1: found Wi-Fi radio killswitch (at 
/sys/devices/pci:00/:00:01.2/:01:00.0/:02:06.0/:08:00.0/ieee80211/phy0/rfkill1)
 (driver iwlwifi)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6445] 
manager[0x556ea1cd8000]: rfkill: Wi-Fi hardware radio set disabled
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6445] 
manager[0x556ea1cd8000]: rfkill: WWAN hardware radio set enabled
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6492] Loaded 
device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-bluetooth.so)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6502] Loaded 
device plugin: NMTeamFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-team.so)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6506] Loaded 
device plugin: NMAtmManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-adsl.so)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6509] Loaded 
device plugin: NMWwanFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-wwan.so)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6514] Loaded 
device plugin: NMWifiFactory 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-device-plugin-wifi.so)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6515] 
manager: rfkill: Wi-Fi enabled by radio killswitch; disabled by state file
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6515] 
manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6516] 
manager: Networking is enabled by state file
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6520] 
settings: Loaded settings plugin: ifupdown 
("/usr/lib/x86_64-linux-gnu/NetworkManager/1.42.4/libnm-settings-plugin-ifupdown.so")
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6520] 
settings: Loaded settings plugin: keyfile (internal)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6520] 
ifupdown: management mode: unmanaged
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6521] 
ifupdown:   interface-parser: parsing file /etc/network/interfaces
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6521] 
ifupdown:   interface-parser: source line includes interfaces file(s) 
/etc/network/interfaces.d/*
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6521] 
ifupdown: interfaces file /etc/network/interfaces.d/* doesn't exist
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6521] 
ifupdown:   interface-parser: finished parsing file /etc/network/interfaces
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6541] dhcp: 
init: Using DHCP client 'internal'
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6543] 
manager: (lo): new Loopback device (/org/freedesktop/NetworkManager/Devices/1)
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6548] device 
(lo): state change: unmanaged -> unavailable (reason 'connection-assumed', 
sys-iface-state: 'external')
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6550] device 
(lo): state change: unavailable -> disconnected (reason 'connection-assumed', 
sys-iface-state: 'external')
aoû 06 09:52:19 station NetworkManager[1195]:   [1722930739.6552] device 
(lo): Activation: starting connection 'lo' 
(5b7cbf4f-0e2b-4686-a86d-d4b92d049df5)
aoû 06 09:52:19

Bug#1074303: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

2024-08-07 Thread pham...@bluewin.ch

Hello,
Listen, I followed your instructions 3x. And 3 times you tell me it's not 
right!?!?
If you are not able to give me correct instructions, you should seriously 
question yourself and consider stopping providing user support, because if you 
don't have the time or patience to take care of it properly, it harms everyone 
including you.
I have applied to the letter the commands you asked me to perform. I just have 
the feeling that you don't care... If you are not able to tell me exactly what 
to do, as is the case, I think it is not worth continuing to waste my time, and 
I sincerely suggest you pass the baton to someone else who is more 
pedagogical...
Greetings.
Message d'origine
De : bi...@debian.org
Date : 06/08/2024 - 18:28 (E)
À : pham...@bluewin.ch, 1074...@bugs.debian.org
Cc : m...@dorfdsl.de
Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when 
booting Debian
Am 06.08.24 um 10:15 schrieb pham...@bluewin.ch: > I hope that this time you 
have the necessary information to work on this > problem. Nope, this is (again) 
not a trace log, thus not possible to make anything useful out of it. For the 
third and last time: read the NetworkManager man page, section "DEBUGGING" and 
follow those instructions.

Bug#1074303: Re: [Pkg-utopia-maintainers] Bug#1074303: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

2024-08-07 Thread pham...@bluewin.ch

I opened a first bug, you asked me to make a diagnosis that was not the right 
one and you closed my bug.
I had to reopen it and 3 times in a row you started asking me to make commands 
to then come and tell me that it is not what you expected of me and then you 
close my bug again!?!
If you do not realize that we do not have the right to do this with people, 
have it explained to you by others than me, because this is too much for me!!
It is me who feels taken for an idiot by you and I tell you clearly, if this 
poses a problem for you it is your story, but you are not doing the job that is 
expected of you as a Debian user impacted by problems ;-(
You should seriously think about questioning yourself !!!
Greetings.
Message d'origine
De : bi...@debian.org
Date : 07/08/2024 - 12:45 (E)
À : pham...@bluewin.ch, 1074303-d...@bugs.debian.org
Objet : Re: [Pkg-utopia-maintainers] Bug#1074303: Re: Bug on Debian 12 Bookworm 
- RJ-45 wired network does not start when booting Debian
[snip rants and insults] such toxic behaviour is not welcome in Debian. I would 
kindly ask you to stop that.

Bug#1072687: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

2024-06-11 Thread pham...@bluewin.ch

Hello,
It is however the dmesg log that Marco Moock asked me for on 06.06.2024 at 
16:30:16 hours.
Tell me exactly which log you need to solve this problem ?
Regards.
Philippe
 
From: Michael Biebl 
> That does not show any NetworkManager specific log messages, i.e. it's 
> not a NetworkManager trace log, thus not useful.
From: Marco Moock 
> Without more information this isn't useful.
> Run dmesg when networking isn't successful and show the output.
From: "pham...@bluewin.ch" 
>> Hello,
>> 
>> Here is the additional information requested.
>> 
>> It should be noted that the Wifi network remains functional @ 1 Gb/s. 
>> Only the RJ-45 network @ 10 Gb/s is impacted by this failure and cannot 
>> be launched. Only a reboot can resolve the problem.
>> 
>> Incidentally, it would be excellent if we could use the tool to 
>> automatically initialize the network during the installation process, 
>> but in post-installation so as to restart it to resolve hardware support 
>> issues.

Bug#1072687: Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

2024-06-11 Thread pham...@bluewin.ch

Hello,

Thank you, I will return the result to you as soon as the problem occurs again.

While I'm at it, do you know if there is a command that can be run to 
re-execute the automatic discovery of network hardware and devices connected to 
it, just like it happens at the beginning of the Debian installation process ? 
By analogy, tasksel allows this regarding the desktop configuration.

Best regards.

Philippe



Message d'origine
De : m...@dorfdsl.de
Date : 11/06/2024 - 09:49 (E)
À : pham...@bluewin.ch, 1072...@bugs.debian.org
Objet : Re: Bug on Debian 12 Bookworm - RJ-45 wired network does not start when 
booting Debian

Am 11.06.2024 um 09:21:55 Uhr schrieb pham...@bluewin.ch:

> Tell me exactly which log you need to solve this problem ?

Please enable trace logging in NetworkManager.
The dmesg doesn't show anything unusual at the first view.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_networking/introduction-to-networkmanager-debugging_configuring-and-managing-networking#temporarily-setting-log-levels-at-run-time-using-nmcli_introduction-to-networkmanager-debugging

nmcli general logging level TRACE domains ALL

Then use 
journalctl -u NetworkManager -b


-- 
Gruß
Marco

Send unsolicited bulk mail to 1718090515mu...@cartoonies.org

Bug#1067054: Debian 12 - Copy files on USB 3

2024-03-17 Thread pham...@bluewin.ch

Package: kernel
Version: 6.1.76-1 (2024-02-01)
Severity: critical

Bug Description:
Good morning,
I noticed a problem with Debian 12 and USB 3.
When I copy a large volume of data +/- 150 Gb onto a 2.5 inch SSD integrated 
into an external enclosure (Satechi) which has a USB 3 type C socket and this 
enclosure is plugged into a USB 3 A socket on my PC, the copy cuts out after a 
while (+/- 20%), there is a crash. If I use a USB 3 C socket on my PC it seems 
to make the problem worse.
Same thing if I restore a 250 GB disk image, it also crashes.
If I do the same restoration job but on a 2 A USB socket, everything works 
perfectly, except that it takes a lot of time...
If I use an M.2 2280 drive also integrated into an external enclosure with a 
USB 3 type C socket, everything works fine.
If I use an SD card connected to an SD card reader connected via USB 3 to my 
machine it also works perfectly.
Debian and its kernel do not seem to appreciate 2.5 inch SSDs integrated into 
external enclosures with a USB 3 type C socket...
Please try to fix this...
Best regards.

Bug#1067054: Debian 12 - Copy files on USB 3

2024-03-17 Thread pham...@bluewin.ch

For complement of information :
The SSD used is a Samsung 850 Pro 256 GB and the case is a Satechi ST-TCDEM. 
Write rates were high at the start of the copy (450 MB/sec then dropped before 
the crash to +/- 30 Mb/sec).
 
 
 Restoring the disk image with this same SSD but integrated in a Delock USB 3 
Type A case to a USB A socket on my computer works correctly with a transfer 
rate of 60 to 90 MB/s.
 
 
The same SSD still plugged into the Delock USB 3 Type A box but connected to my 
machine on a USB C port completes the restoration of the image with a constant 
transfer rate of +/- 41MB/sec.
Regards.

Bug#1067054: Re: Bug#1067054: Debian 12 - Copy files on USB 3

2024-03-18 Thread pham...@bluewin.ch

>What you're describing sounds just as likely to be a hardware problem
>with the enclosure, to be honest. Does it work 100% reliably elsewhere?

Hello Steve,

I recently spoke on a forum with a user who also had a USB C box from another 
brand and who had the same problem as mine...

So the problem doesn't seem to only concern me.

Under Windows 11 there is no problem, everything works perfectly. The transfer 
takes place everywhere at 400 MB/sec. So it's not a hardware problem contrary 
to what you say.

I will soon receive a 2.5 inch USB C drive enclosure from another brand. I can 
do tests again if you want but the result will be the same, that's for sure!!

For my part, I more than strongly suspect a teething problem with the USB 3 
type C driver under Linux...

Regard.

Philippe

Bug#1067054: Debian 12 - Copy files on USB 3

2024-03-28 Thread pham...@bluewin.ch

After further testing, the crash issue when copying multiple files (total 
volume 150 GB) or a disk image (250 GB) is present when an SSD is formatted in 
GPT format. 
This works without problem if the SSD is formatted in MBR/MS-DOS.
Regards.

Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work

2024-05-08 Thread pham...@bluewin.ch

Package:  Gnome-Shell
Version: 43.9-0+deb12u2
Severity: critical

Bug Description:
After today's update, the dead keys on my keyboard no longer work, neither on 
my workstation or on my laptop ?!?
I noticed this problem on my station this morning after the proposed update.
I checked that it worked well on my laptop everything was ok, I applied the 
update and after a reboot it no longer worked on my laptop either.
- Station update log :
Start-Date: 2024-05-08  09:17:44
Commandline: apt dist-upgrade
Upgrade: libglib2.0-bin:amd64 (2.74.6-2, 2.74.6-2+deb12u1), 
libglib2.0-data:amd64 (2.74.6-2, 2.74.6-2+deb12u1), gnome-shell:amd64 
(43.9-0+deb12u1, 43.9-0+deb12u2), gnome-shell-common:amd64 (43.9-0+deb12u1, 
43.9-0+deb12u2), libglib2.0-0:amd64 (2.74.6-2, 2.74.6-2+deb12u1), 
libglib2.0-0:i386 (2.74.6-2, 2.74.6-2+deb12u1), 
gnome-shell-extension-prefs:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2)
Remove: linux-image-6.1.0-18-amd64:amd64 (6.1.76-1)
End-Date: 2024-05-08  09:17:52
- Laptop update log :
Start-Date: 2024-05-08  11:07:48
Commandline: apt dist-upgrade -y
Install: linux-headers-6.1.0-21-amd64:amd64 (6.1.90-1, automatic), 
linux-headers-6.1.0-21-common:amd64 (6.1.90-1, automatic), 
linux-image-6.1.0-21-amd64:amd64 (6.1.90-1, automatic)
Upgrade: libglib2.0-bin:amd64 (2.74.6-2, 2.74.6-2+deb12u1), 
linux-compiler-gcc-12-x86:amd64 (6.1.85-1, 6.1.90-1), linux-headers-amd64:amd64 
(6.1.85-1, 6.1.90-1), libglib2.0-data:amd64 (2.74.6-2, 2.74.6-2+deb12u1), 
gnome-shell:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), linux-kbuild-6.1:amd64 
(6.1.85-1, 6.1.90-1), linux-image-amd64:amd64 (6.1.85-1, 6.1.90-1), 
gnome-shell-common:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), libglib2.0-0:amd64 
(2.74.6-2, 2.74.6-2+deb12u1), libglib2.0-0:i386 (2.74.6-2, 2.74.6-2+deb12u1), 
gnome-shell-extension-prefs:amd64 (43.9-0+deb12u1, 43.9-0+deb12u2), 
linux-libc-dev:amd64 (6.1.85-1, 6.1.90-1)
End-Date: 2024-05-08  11:08:10
Thank you for urgently returning to previous versions, we can no longer work 
properly since...
Regards.

Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work

2024-05-08 Thread pham...@bluewin.ch

Post Scriptum
I use Swiss French/German/Italian keyboard.
We have a unique keyboard for these 3 languages.
I have tested all existing keyboard profiles without success. They all pose 
this problem.
If I enter for exemple : être 
The result displayed is : tre
The keyboard option without dead keys works but is unusable on a daily basis.
Regards.

Bug#1070745: Re: Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After today's upgrade, the dead keys on my keyboard no longer work

2024-05-08 Thread pham...@bluewin.ch

Thank you a thousand times Simon for your extremely quick response :)

I'm looking forward to the fix...

Good day to you.

Philippe


Message d'origine
De : s...@debian.org
Date : 08/05/2024 - 12:41 (E)
À : pham...@bluewin.ch, 1070...@bugs.debian.org
Objet : Re: Bug#1070745: Bug on Debian 12 Bookworm - Gnome-Shell / After 
today's upgrade, the dead keys on my keyboard no longer work

Control: reassign -1 libglib2.0-0 2.74.6-2+deb12u1
Control: affects -1 + gnome-shell

On Wed, 08 May 2024 at 11:42:10 +0200, pham...@bluewin.ch wrote:
> After today's update, the dead keys on my keyboard no longer work

This is a regression in GLib triggered by fixing CVE-2024-34397. I'm
testing a possible fix as rapidly as I can, but each GLib build takes
about an hour, so please be patient.

smcv

Bug#1067054: Debian 12 - Copy files on USB 3

2024-04-16 Thread pham...@bluewin.ch

Extra information :
It is stable when you initialize the disk in MBR/MS-DOS format, but only with a 
USB A to USB C cable, if you use a USB c to USB-C cable the problems persist.

Bug#1074303: I have activated:Bug on Debian 12 Bookworm - RJ-45 wired network does not start when booting Debian

2024-07-02 Thread pham...@bluewin.ch

I have activated : 
nmcli general logging level TRACE domains ALL
I hadn't noticed this specific request... the bug system is not very readable 
and my native language is not English.
How to put it back to normal mode after ?
I'll send you more information as soon as the bug reappears, in a few weeks 
because it's summer vacation...
Please don't close this bug.
Regards.

Bug#1030984: Bug on Debian 11 Bullseye - Kernel 5.9 and up - linux-image amd64

2023-02-09 Thread pham...@bluewin.ch

Package:  linux-image amd64
Version: 5.9 and up to linux-image amd64
NVIDIA drivers version: NVIDIA-Linux-x86_64-525.89.02.run

Bug Description:
Hello,
Since kernel 5.9 it has become very complicated to install recent Nvidia 
drivers.
With kernel 5.8 and earlier it was enough to do : 
/etc/init.d/*dm stop
cd ..
cd /home/username/Download
sh ./NVIDIA-Linux-x86_64-455.38.run
Since Kernel 5.9 I can no longer install the Nvidia drivers directly on these 
recent kernels, or I have an error message that appears on reboot indicating 
that lightdm (from Cinnamon) could not start.
To work around this problem I must have the 5.10.x kernel installed. Then I 
have to remove the 6.1.x kernel from my system and reboot to 5.10.x. After that 
I can install the latest Nvidia driver, then once this process is finished, 
after the next reboot I can reinstall the 6.1.x kernel with it headers and 
finally reboot on it.
I need to specify to the system that Kernel 5.10 was installed manually, 
otherwise it is deleted after running the command :
apt-get clean && apt-get autoclean && apt-get autoremove -y
And in this situation the Kernel 5.10.x does not update automatically anymore 
;-(
In short since kernel 5.9 the situation has become complicated and I lose at 
least 20 minutes each time I have to update this Nvidia graphics driver ;-(
Thank you for seeing what is happening and for trying to lighten the 
arduousness of the tasks to be performed to carry out a simple update of these 
drivers...
There is another problem when you want to resoft a machine using the advanced 
options of the Debian installer and you select the kernel from Backports 6 or 
higher (with firmware and headers). Theoretically, this should support an Intel 
AX201 Wifi card and provide access to the local network as well as the 
Internet. But unfortunately, it doesn't work, the Backport kernel installs 
correctly, but recent hardware (Intel AX201) is not recognized when it should 
be and no network or internet access is possible on my laptop Dell 9520.   
Best regards.

Philippe

Bug#1020504: Bug on Debian 11 Bullseye - Kernel 5.19.6-amd64 dont run with Nvidia drivers

2022-09-22 Thread pham...@bluewin.ch

Package: linux-image-5.19.0-1-amd64 
Version: 5.19.6-1 
Nvidia drivers version: 515.65.01 & 515.76 from Nvidia web site

Bug Description: 
The installation of the Nvidia drivers is done perfectly from the kernel 
5.10.140-1, but it is impossible to boot then on kernel 5.19.6-1.
If you try to install the drivers from kernel 5.10.140-1, it ends in failure.
The problem occurs with Nvidia drivers 515.65.01 & 515.76 from Nvidia web site. 
This happens whether you choose the option of installing proprietary drivers or 
free drivers.
I am delighted that future Nvidia drivers will soon be included in the Linux 
Kernel, it will require less maintenance from users and it will offer us more 
stability on our systems...
Best regards.

Philippe

Bug#1022118: Cannot update on Debian 11 Stable with Secure Boot dbx 83 => 217

2022-10-20 Thread pham...@bluewin.ch

Package: fwupd
Version: 1.5.7-4 
Bug Description: 
Gnome software tells me that a Secure Boot dbx 83 => 217 update is available 
but the update is impossible to perform.
This problem has been present for several weeks and no update has been released.
A another version available (Debian Testing) v. 1.8.6-2+b1, but this version is 
impossible to use, due to broken/incomplete package dependencies.
fwupdmgr --version :
client version: 1.5.7
compile-time dependency versions
gusb: 0.3.5
fwupdmgr get-devices --show-all-devices :
XPS 15 9570
│
├─GP107M [GeForce GTX 1050 Ti Mobile]:
│ Device ID: ce4c74a5188d5b9cdb1e72ed32dad2d313c1c999
│ Version actuelle: a1
│ Fournisseur: NVIDIA Corporation (PCI:0x10DE)
│ GUIDs: a29c3564-3d3b-5ce2-9616-4567cb1d9670
│ 2d6a79d7-4ac2-53fd-af2d-000e2dfbdc68
│ dc1e6866-2188-547f-b175-35e07dd7a6af
│ 04232c57-d805-551d-a1de-1bba9350d71f
│ Device Flags: • Périphérique interne
│ • Cryptographic hash verification is available
│
├─Intel(R) Core™ i7-8750H CPU @ 2.20GHz:
│ Device ID: 4bde70ba4e39b28f9eab1628f9dd6e6244c03027
│ Version actuelle: 0x00f0
│ Fournisseur: Intel
│ GUIDs: b9a2dd81-159e-5537-a7db-e7101d164d3f
│ 30249f37-d140-5d3e-9319-186b1bd5cac3
│ 809a0b93-8a12-5338-a571-ad5583acf896
│ 72ec2ff3-49ff-5ec2-bdbb-525badd47543
│ Device Flags: • Périphérique interne
│
├─Samsung SSD 970 EVO 2TB:
│ Device ID: f2759da7fe8e0388c5f3601cb072f837b1070b03
│ Résumé: NVM Express Solid State Drive
│ Version actuelle: 2B2QEXE7
│ Fournisseur: Samsung Electronics Co Ltd (NVME:0x144D)
│ GUIDs: 0b4d773a-7ac3-58c1-a541-e22ef1cdfe02
│ c9d531ea-ee7d-5562-8def-c64d0d144813
│ 6e54c992-d302-59ab-b454-2d26ddd63e6d
│ 47335265-a509-51f7-841e-1c94911af66b
│ 4494b540-d91c-5ae9-9963-3b0f03e7fe2b
│ Device Flags: • Périphérique interne
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
├─System Firmware:
│ │ Device ID: 66352e92895dc6d018071ad4ecfae249b0b8af0d
│ │ Version actuelle: 1.27.0
│ │ Version minimum: 1.27.0
│ │ Fournisseur: Dell Inc. (DMI:Dell Inc.)
│ │ GUIDs: e4d7bdc4-cc95-4aa0-a982-5e915fc04bf0
│ │ 230c8b18-8d9b-53ec-838b-6cfc0383493a
│ │ 127676e3-b872-5f45-83d2-de29b06d8dfd
│ │ Device Flags: • Périphérique interne
│ │ • Updatable
│ │ • System requires external power source
│ │ • Supported on remote server
│ │ • Needs a reboot after installation
│ │ • Cryptographic hash verification is available
│ │ • Device is usable for the duration of the update
│ │
│ ├─Intel AMT [unprovisioned]:
│ │ Device ID: e2623122c99d58220498aacbfcfdb1baebbae3c5
│ │ Résumé: Hardware and firmware technology for remote out-of-band management
│ │ Version actuelle: 12.0.90.2072
│ │ Version du chargeur d’amorçage:12.0.90.2072
│ │ Fournisseur: Intel Corporation
│ │ GUID: 2800f812-b7b4-2d4b-aca8-46e0ff65814c
│ │ Device Flags: • Périphérique interne
│ │
│ └─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Résumé: UEFI Revocation Database
│ Version actuelle: 83
│ Version minimum: 83
│ Fournisseur: UEFI:Linux Foundation
│ Install Duration: 1 seconde
│ GUIDs: 00fe3755-a4d8-5ef7-ba5f-47979fbb3423
│ 4a6cd2cb-8741-5257-9d1f-89a275dacca7
│ c6682ade-b5ec-57c4-b687-676351208742
│ f8ba2887-9411-5c36-9cee-88995bb39731
│ Device Flags: • Périphérique interne
│ • Updatable
│ • Supported on remote server
│ • Needs a reboot after installation
│
├─TPM:
│ │ Device ID: c6a80ac3a22083423992a3cb15018989f37834d6
│ │ Version actuelle: 7.2.0.2
│ │ Fournisseur: Nuvoton Technology (TPM:NTC|PCI:0x1028)
│ │ GUIDs: ff71992e-52f7-5eea-94ef-883e56e034c6
│ │ fac1c8f3-73c8-5cd6-8330-07a3690b5140
│ │ bdb182b9-7533-5c43-b775-0c8327246042
│ │ e9ccc1dc-960a-5e09-afe9-e59a904b776d
│ │ 31c399b3-9c72-58ce-8fc3-489e76ab1e35
│ │ Device Flags: • Périphérique interne
│ │
│ └─Event Log:
│ Device ID: 58bd405f31c48e6eca290b425f530a94c91e955c
│ GUID: a25657fe-b5dc-5be0-8b78-8b9dfec678ff
│ Device Flags: • Périphérique interne
│
├─UHD Graphics 630 (Mobile):
│ Device ID: 5792b48846ce271fab11c4a545f7a3df0d36e00a
│ Fournisseur: Intel Corporation (PCI:0x8086)
│ GUIDs: 05714aa3-3a30-5606-ba13-ab4f1a48721a
│ 4d089443-bd6e-58f7-b664-d506e9ebe075
│ 12c60b98-52cd-500a-b99e-087aa6b47f0b
│ db677673-1102-5481-a11e-6f397e123ced
│ Device Flags: • Périphérique interne
│ • Cryptographic hash verification is available
│
└─USB2.0 Hub:
Device ID: b6bcdb236926a2452b472d3dad455c414145b52e
Résumé: USB 2.x Hub
Version actuelle: 90.33
Fournisseur: VIA Labs, Inc. (USB:0x2109)
Install Duration: 15 secondes
GUIDs: a391c569-168c-5516-ac60-207b4c597f36
0b3d95fe-5e53-5b5f-ad53-939138d026ff
32989214-b2d1-5902-a3fc-b90a5536b190
009c01ea-7f60-5bb9-a94b-326f460cdddf
aa831a2f-63a6-5689-8358-4e5d041c8d40
6f3b120d-c948-5a52-987a-bf212d152948
Device Flags: • Updatable
• Cryptographic hash verification is available
• Device stages updates
• Device can recover flash failures
Devices that were not updated correctly:
• UEFI dbx (83 → 217)
Uploading firmware reports helps hardware vendors to quickly identify failing

Bug#1035305: Re: Bug#1035305: Bugs on Debian 12 RC2

2023-05-01 Thread pham...@bluewin.ch

Hello Cyril,
Apart from what I quoted to you, the installer works correctly.
However, there is another major bug (excluding installation) that I noticed, 
the command lines below do not work with this RC2, they generate a whole series 
of errors:
add-apt-repository "deb https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar main" && apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
0AB215679C571D1C8325275B9BDB3D89CE49EC21 && apt update && apt install firefox -y
add-apt-repository "deb https://ppa.launchpad.net/vincent-vandevyvre/vvv/ubuntu 
lunar main" && apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
7CAA00CD3DCA73E24812D646A5ADEEFF89F92A1A && apt update && apt install qarte -y
I would have been delighted if progress had been made on the other points I 
raised (WPA3 support and boot files installing on the /boot/efi partition of 
Windows and not Debian). But reading you I'm afraid it won't happen in Debian 
12, which I deeply regret ;-(
I am also very surprised that the Nvidia drivers have not been integrated into 
this RC2. This greatly limits the possibility of migrating to this RC2 to 
perform more in-depth tests with machines with only one Nvidia card available.
Best regards and good continuation to you.
This message has been translated from French to English via google translate.
Philippe
Message d'origine
De : k...@debian.org
Date : 30/04/2023 - 16:59 (E)
À : 1035...@bugs.debian.org
Cc : pham...@bluewin.ch
Objet : Re: Bug#1035305: Bugs on Debian 12 RC2
Control: retitle -1 Bugs on Debian 12 RC2
Control: submitter -1 pham...@bluewin.ch
Hi Philippe,
pham...@bluewin.ch 
 (2023-04-29):
> Configure network: [ X]
> 
> - WAP3 support from the installer is required. My Laptop (Dell XPS
> 9520) does not have an RJ-45 connection, it only has Wifi available
> like many machines today. My router is configured in WAP3 only... This
> complicates things a lot during installation.
To reiterate my answer from debian-boot@ earlier[1], we don't support
WPA3 in the installer yet (now tracked via #1035306[2]). Be it within the
installer or outside it, a custom workaround when native connectivity
isn't working (for whatever reason) is using an USB-to-Ethernet adapter.
  1. https://lists.debian.org/debian-boot/2023/04/msg00351.html
  2. https://bugs.debian.org/1035306
> - The problem to solve which is present in all intermediate versions
> of Debian is related to sources.list. It lacks the following
> information :
> 
> # Bookworm base repository
> deb https://deb.debian.org/debian bookworm main non-free-firmware
> deb-src https://deb.debian.org/debian bookworm main non-free-firmware
> #
> # Bookworm-updates
> deb https://deb.debian.org/debian bookworm-updates main non-free-firmware
> deb-src https://deb.debian.org/debian bookworm-updates main non-free-firmware
> # 
> # Security updates
> deb https://deb.debian.org/debian-security/ bookworm-security main 
> non-free-firmware
> deb-src https://deb.debian.org/debian-security/ bookworm-security main 
> non-free-firmware
> #
> # Proposed-updates (versions intermédiaires)
> # deb https://deb.debian.org/debian bookworm-proposed-updates main contrib 
> non-free-firmware
> # deb-src https://deb.debian.org/debian bookworm-proposed-updates main 
> contrib non-free-firmware
I suspect this is a “just” a side-effect of having no network in the
installer (lack of WPA3 and no alternative connectivity); the problem I
was alluding to earlier was the absence of bookworm-updates specifically
(fixed in RC 2), and that's indeed a separate topic.
> - Under Cinnamon if I deactivate the Wifi network via the taskbar, at
> the next boot it is automatically reactivated (installation on an
> external hard drive for testing). After an installation on the
> internal ssd of my laptop, the problem no longer occurs !?
I'll let others comment here, this seems weird to me.
> Install boot loader: [ X]
Dual-/multi-booting isn't my area.
> Overall install: [X ]
> 
> - After testing RC2 on my workstation, I have problems installing
> Nvidia graphics drivers for my RTX 3080. Nvidia detect does not seem
> to be present and Nvidia-drivers refuses to install, it only shows the
> available version n c isn't the right one ??
> 
> - The 'reboot' command does not work in simple user, only in root ;-(
Those are definitely not installer-related topics; the former should
probably be a bug report against one of the nvidia package; the latter
isn't a bug.
Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant

Bug#1037325: Bug on Debian 11 Bookworm - Installation-reports - EFI partition installation

2023-06-11 Thread pham...@bluewin.ch

Package: Installation-reports - EFI partition installation
Severity: Hight

Bug Description:

In manual installation mode with 2 SSD present on my laptop (an SSD with 
Windows 11 with an EFI partition of 100 MB, an SSD for Debian 12 with an EFI 
partition of 500 MB), the Debian 12 installer refuses to use the 500 MB EFI 
partition of the SSD from Debian 12 and installs on the 100 MB EFI partition of 
the SSD from WIndows 11.
After installation, the 100 MB EFI partition of the WIndows 11 SSD being almost 
full, I have no possibility of installing other OSes ;-( This 100 MB partition 
being ridiculously small and not expandable, it does not also cannot benefit 
from effective support of the TRIM function.
Thank you for correct this as soon as possible.
Best regards.

Philippe

Bug#1037328: Bug on Debian 12 Bookworm - Installation-reports - EFI partition installation

2023-06-11 Thread pham...@bluewin.ch

Package: Installation-reports - EFI partition installation
Severity: High

Bug Description:

In manual installation mode with 2 SSD present on my laptop (an SSD with 
Windows 11 with an EFI partition of 100 MB, an SSD for Debian 12 with an EFI 
partition of 500 MB), the Debian 12 installer refuses to use the 500 MB EFI 
partition of the SSD from Debian 12 and installs on the 100 MB EFI partition of 
the SSD from WIndows 11.
After installation, the 100 MB EFI partition of the WIndows 11 SSD being almost 
full, I have no possibility of installing other OSes ;-( This 100 MB partition 
being ridiculously small and not expandable, it does not also cannot benefit 
from effective support of the TRIM function.
Thank you for correct this as soon as possible.
Best regards.

Philippe

Bug#1037482: Bug on Debian 12 Bookworm - add-apt-repository not work

2023-06-13 Thread pham...@bluewin.ch

Package:  add-apt-repository
Version: ?
Severity: high

Bug Description:

This command, which no longer allows you to add external repositories, worked 
perfectly under Debian 10 & 11, but it no longer works under Debian 12.
Command to add Mozilla Firefox official ppa :
add-apt-repository "deb http://ppa.launchpad.net/mozillateam/ppa/ubuntu focal 
main"
apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 
0AB215679C571D1C8325275B9BDB3D89CE49EC21
Now it generates errors :
root@station:~# add-apt-repository "deb 
http://ppa.launchpad.net/mozillateam/ppa/ubuntu lunar main"
Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 362, in 
sys.exit(0 if addaptrepo.main() else 1)
  ^
  File "/usr/bin/add-apt-repository", line 345, in main
shortcut = handler(source, **shortcut_params)
   ^^
  File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
40, in shortcut_handler
return handler(shortcut, **kwargs)
   ^^^
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 78, in 
__init__
self.lpppa
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 126, in 
lpppa
self._lpppa = self.lpteam.getPPAByName(name=self.ppaname)
  ^^^
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 113, in 
lpteam
self._lpteam = self.lp.people(self.teamname)
   ^^
AttributeError: 'NoneType' object has no attribute 'people'
Thank you to correct this as soon as possible.
Best regards.

Philippe

Bug#1037972: Bug on Debian 12 Bookworm - Installation reports - /etc/apt/source.list

2023-06-14 Thread pham...@bluewin.ch

Package: debian-12.0.0-amd64-DVD-1.iso
File: /etc/apt/source.list
Severity: high (security)

Bug Description :

After installation of Debian 12 with the 'debian-12.0.0-amd64-DVD-1.iso' image, 
the '/etc/apt/source.list' file contains only one entry for installing or 
upgrading the system:
deb cdrom:[Debian GNU/Linux 12.0.0 _Bookworm_ - Official amd64 DVD Binary-1 
with firmware 20230610-10:23]/ bookworm main non-free-firmware
After editing the 'source.list' file with the 'software and updates' software 
and activating all remote repositories of the first tab of this program, only 
one line is added to the 'source.list' file ':
deb https://deb.debian.org/debian/ bookworm main contrib non-free 
non-free-firmware
It therefore lacks parameters to perform updates / security repertories on this 
DVD version of 'source.list' file, while in the Live ISO version of Debian 12 
Cinnamon does not have this type of problem.
Someone who doesn't know Debian and has installed the DVD edition of Debian on 
a machine can find themselves really embarrassed some time later since the 
security updates for their machine are not done without manually updating 
update the 'source.list' file.
Thank you to correct this as soon as possible.
Best regards.
Philippe

Bug#1039009: Bug on Debian 12 Bookworm - nvidia-driver 525.105.17-1

2023-06-24 Thread pham...@bluewin.ch

Package: nvidia-driver 525.105.17-1
Severity: important

Bug Description :
I have a Dell XPS 9520 laptop which has two Intel / Nvidia graphics cards and 
runs Debian 12. When I only use free drivers my laptop has good battery life.
When I install the proprietary Nvidia driver, even though Debian uses the free 
driver, the power consumption goes up by +/- 30%.
With the Cinnamon desktop, in "System Settings" there is an Nvidia icon that 
appears after installing the driver. But when I click on it, I can't configure 
anything. While on Ubuntu or Mangaro in this place I can choose which GPU to 
use by default, which is not possible on Debian ;-(
Therefore it is impossible for me to use the Nvidia driver even once installed 
via the GUI interface?? I saw there are solutions to launch apps from the 
command line, for example via Bumblebee, this is too complicated to use for an 
uninitiated person like my daughter.
Please try to make Nvidia drivers easier to use in the future on laptops with 2 
integrated GPUs running Debian...
Best regards.
Philippe

Bug#989777: Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

2021-06-12 Thread pham...@bluewin.ch

Package: kernel 
Version: 5.10.x-amd64
Bug Description: My Intel AX210 Wifi and Bluetooth card not work
Intel indicates on its website that this AX210 card is compatible from kernel 
5.10 !?!
https://www.intel.com/content/www/us/en/support/articles/05511/wireless.html
My laptop does not have an RJ-45 port, I do not have access to the internet, 
nor to my Bluetooth devices such as my mouse, my keyboard, my headphones ;-(
Best regards.
Philippe

Bug#989777: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

Hello and thank you for your message.
I'm already using the "non-free" Debian images which contain firmware for 
network cards etc.
https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-dvd/
The package "firmware-iwlwifi_20210315-2_all.deb" is correctly installed, but 
my Intel AX210 Wifi / Bluetooth card is not recognized and is not functional.
This problem is extremely debilitating for me (severity: high). I bought this 
hardware to run on Debian 10 with Backport and on Debian 11 but I cannot use it.
Best regards.
Philippe

Bug#989777: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

Hello Vincent,
And thank you for your message.
I just tested the two new live images:
- debian-live-blsy-DI-rc2-amd64-cinnamon+nonfree.iso2021-06-11 
18:133.2G
- debian-live-testing-amd64-cinnamon+nonfree.iso2021-06-14 
07:553.2G
Both work with firmware iwlwifi_20210315-2 so they don't work on my system.
I don't know where to find a version of Debian 11 live including the old 
firmware_iwlwifi 20210208-4 you are telling me about.
I would like to do a test for you if you provide me with a download URL of a 
live version of Debian 11 equipped with this firmware_iwlwifi 20210208-4. 
Also note that I can't seem to find a download link for 
firmware_iwlwifi_20210208-4.deb alone.
Meilleures salutations / Best regards.
Philippe

Bug#989777: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

Hello Andrei,
I must have "my head in the moon" as we say in French :) I did not see the 
download link...
After uninstall of the new "firmware-iwlwifi_20210315-2_all.deb" and 
installation of the old "firmware-iwlwifi_20210208-4_all.deb" the Wifi work 
fine, but the Bluetooth not work, I dont have access to my Bluetooth devices ;-(
Best regards.
Philippe

Bug#989777: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

Salut Vincent,

I have rebooted my Laptop after downgrading the firmware, this must have 
restarted the iwlmvm and iwlwifi services, which allowed me to launch an 
internet connection by Wifi.

But nothing to do for Bluetooth, it refuses to work.

Regards.

Philippe



Message d'origine
De : vincent.deb...@free.fr
Date : 14/06/2021 - 21:59 (E)
À : pham...@bluewin.ch
Cc : andreimpope...@gmail.com, 989...@bugs.debian.org, li...@packages.debian.org
Objet : Re: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => 
Intel AX210 Wifi & Bluetooth not work

Salut Philippe,

Le 2021-06-14 21:48, pham...@bluewin.ch a écrit :
> Hello Andrei,
> I must have "my head in the moon" as we say in French :) I did not see the 
> download link...
> After uninstall of the new "firmware-iwlwifi_20210315-2_all.deb" and 
> installation of the old "firmware-iwlwifi_20210208-4_all.deb" the Wifi work 
> fine, but the Bluetooth not work, I dont have access to my Bluetooth devices 
> ;-(

Did you reload the iwlmvm and iwlwifi modules after downgrading the firmware?

> Best regards.
> Philippe

Cheers,
Vincent

Bug#989777: Re: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

The boot is difficult, I have a recurring error message that turns in a loop.

journalctl -k | grep -Ei "iwl|bluetooth :


root@portable-1:~# journalctl -k | grep -Ei "iwl|bluetooth"
jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: enabling device ( 
-> 0002)
jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: firmware: 
direct-loading firmware iwlwifi-ty-a0-gf-a0-59.ucode
jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: api flags index 2 
larger than supported by driver
jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: TLV_FW_FSEQ_VERSION: 
FSEQ Version: 93.8.63.28
jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: loaded firmware 
version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: firmware: failed to 
load iwl-debug-yoyo.bin (-2)
jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: Detected Intel(R) 
Wi-Fi 6 AX210 160MHz, REV=0x420
jun 14 22:48:12 portable-1 kernel: Bluetooth: Core ver 2.22
jun 14 22:48:12 portable-1 kernel: Bluetooth: HCI device and connection manager 
initialized
jun 14 22:48:12 portable-1 kernel: Bluetooth: HCI socket layer initialized
jun 14 22:48:12 portable-1 kernel: Bluetooth: L2CAP socket layer initialized
jun 14 22:48:12 portable-1 kernel: Bluetooth: SCO socket layer initialized
jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: firmware: failed to 
load iwlwifi-ty-a0-gf-a0.pnvm (-2)
jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: base HW address: 
54:14:f3:52:7b:e1
jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
information failed (-22)
jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
(-22)
jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
FW download
jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0 wlp59s0: renamed from 
wlan0
jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP filters: protocol multicast
jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP socket layer initialized
jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
information failed (-22)
jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
(-22)
jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
FW download
jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
information failed (-22)
jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
(-22)
jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
FW download


systemctl status bluetooth.service :


root@portable-1:~# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Mon 2021-06-14 22:48:12 CEST; 10min ago
   Docs: man:bluetoothd(8)
   Main PID: 649 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 38030)
 Memory: 2.6M
CPU: 266ms
 CGroup: /system.slice/bluetooth.service
 └─649 /usr/libexec/bluetooth/bluetoothd

jun 14 22:48:12 portable-1 bluetoothd[649]: 
src/main.c:parse_controller_config() Key file does not have key 
“LEScanIntervalConnect” in >
jun 14 22:48:12 portable-1 bluetoothd[649]: 
src/main.c:parse_controller_config() Key file does not have key 
“LEScanWindowConnect” in gr>
jun 14 22:48:12 portable-1 bluetoothd[649]: 
src/main.c:parse_controller_config() Key file does not have key 
“LEMinConnectionInterval” i>
jun 14 22:48:12 portable-1 bluetoothd[649]: 
src/main.c:parse_controller_config() Key file does not have key 
“LEMaxConnectionInterval” i>
jun 14 22:48:12 portable-1 bluetoothd[649]: 
src/main.c:parse_controller_config() Key file does not have key 
“LEConnectionLatency” in gr>
jun 14 22:48:12 portable-1 bluetoothd[649]: 
src/main.c:parse_controller_config() Key file does not have key 
“LEConnectionSupervisionTim>
jun 14 22:48:12 portable-1 bluetoothd[649]: 
src/main.c:parse_controller_config() Key file does not have key 
“LEAutoconnecttimeout” in g>
jun 14 22:48:12 portable-1 systemd[1]: Started Bluetooth service.
jun 14 22:48:12 portable-1 bluetoothd[649]: Starting SDP server
jun 14 22:48:12 portable-1 bluetoothd[649]: Bluetooth management interface 1.18 
initialized
lines 1-22/22 (END)


If I can be useful for make a test on my system, do not hesitate to ask me it.

Meilleures salutations.

Philippe



Message d'origine
De : vincent.deb...@free.fr
Date : 14/06/2021 - 22:38 (E)
À : pham...@bluewin.ch
Cc : li...@packages.debian.org, 989...@bugs.debian.org, andreimpope...@gmail.com
Objet : Re: Severity: High / Debian 10 &amp; 11 with Kernel 5.10.x-amd64 
=&gt; Intel AX210 Wifi &amp; Bluetooth not work

Le 2021-06-14 22:19, pham...@bluewin.

Bug#989777: Re: Re: Severity: High / Debian 10 &amp; 11 with Kernel 5.10.x-amd64 =&gt; Intel AX210 Wifi &amp; Bluetooth not work

2021-06-18 Thread pham...@bluewin.ch

Salut Vincent,

Thanks for these informations.

Does this mean that I have a chance of seeing a patch arrive on Debian's 5.10 
LTS kernel ?

Or is it better for me that I migrate to Ubuntu while waiting for the 
availability of a kernel 5.11 or higher in the Backports directory ?

I'm not really a fan of Ubuntu and even less of its Snap packages for Chromium 
and other softwares.

What bothers me the most in this story is that Intel guarantees us on its 
website compatibility with Kernel 5.10, which is why I bought this material and 
in the end it is not ;-( If j had known I would have chosen another material...

I wish you a great weekend.

Meilleures salutations.

Philippe


Message d'origine
De : vincent.deb...@free.fr
Date : 17/06/2021 - 22:15 (E)
À : pham...@bluewin.ch
Cc : andreimpope...@gmail.com, 989...@bugs.debian.org, li...@packages.debian.org
Objet : Re: Re: Severity: High / Debian 10 &amp;amp; 11 with Kernel 
5.10.x-amd64 =&amp;gt; Intel AX210 Wifi &amp;amp; Bluetooth not work

Salut Philippe,

Le 2021-06-14 23:09, pham...@bluewin.ch a écrit :
> The boot is difficult, I have a recurring error message that turns in a loop.
> 
> journalctl -k | grep -Ei "iwl|bluetooth :
> 
> 
> root@portable-1:~# journalctl -k | grep -Ei "iwl|bluetooth"
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: enabling device 
> ( -> 0002)
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: firmware: 
> direct-loading firmware iwlwifi-ty-a0-gf-a0-59.ucode
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: api flags index 2 
> larger than supported by driver
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: TLV_FW_FSEQ_VERSION: 
> FSEQ Version: 93.8.63.28
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: loaded firmware 
> version 59.601f3a66.0 ty-a0-gf-a0-59.ucode op_mode iwlmvm
> jun 14 22:48:11 portable-1 kernel: iwlwifi :3b:00.0: firmware: failed to 
> load iwl-debug-yoyo.bin (-2)
> jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: Detected Intel(R) 
> Wi-Fi 6 AX210 160MHz, REV=0x420
> jun 14 22:48:12 portable-1 kernel: Bluetooth: Core ver 2.22
> jun 14 22:48:12 portable-1 kernel: Bluetooth: HCI device and connection 
> manager initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: HCI socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: L2CAP socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: SCO socket layer initialized
> jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: firmware: failed to 
> load iwlwifi-ty-a0-gf-a0.pnvm (-2)
> jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0: base HW address: 
> 54:14:f3:52:7b:e1
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
> information failed (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
> (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
> FW download
> jun 14 22:48:12 portable-1 kernel: iwlwifi :3b:00.0 wlp59s0: renamed from 
> wlan0
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 
> 1.3
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP filters: protocol multicast
> jun 14 22:48:12 portable-1 kernel: Bluetooth: BNEP socket layer initialized
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
> information failed (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
> (-22)
> jun 14 22:48:12 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
> FW download
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Reading Intel version 
> information failed (-22)
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Intel Read version failed 
> (-22)
> jun 14 22:48:13 portable-1 kernel: Bluetooth: hci0: Intel reset sent to retry 
> FW download
> 
> 
> systemctl status bluetooth.service :
> 
> 
> root@portable-1:~# systemctl status bluetooth.service
> ● bluetooth.service - Bluetooth service
>  Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
> preset: enabled)
>  Active: active (running) since Mon 2021-06-14 22:48:12 CEST; 10min ago
>Docs: man:bluetoothd(8)
>Main PID: 649 (bluetoothd)
>  Status: "Running"
>   Tasks: 1 (limit: 38030)
>  Memory: 2.6M
> CPU: 266ms
>  CGroup: /system.slice/bluetooth.service
>  └─649 /usr/libexec/bluetooth/bluetoothd
> 
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key file does not have key 
> “LEScanIntervalConnect” in >
> jun 14 22:48:12 portable-1 bluetoothd[649]: 
> src/main.c:parse_controller_config() Key fi

Bug#989777: Re: Re: Severity: High / Debian 10 &amp; 11 with Kernel 5.10.x-amd64 =&gt; Intel AX210 Wifi &amp; Bluetooth not work

2021-06-18 Thread pham...@bluewin.ch

Salut Vincent,

I have found this way of doing things without having tested it yet, maybe it 
will allow Debian 11 to be compatible with my Wifi / Bluetooth card without 
having to install a future 5.11 kernel from backports ??

If you could get basic compatibility with the 5.10 kernel for bluetooth in 
addition to wifi, that would be really good.

Best regards.

Philippe


https://askubuntu.com/questions/1326386/ubuntu-20-04-lts-driver-intel-wi-fi-6e-ax210-160mhz


I actually managed to make the AX210 run in Ubuntu 18.04 LTS with Linux Kernel 
4.15! Here's what I did:

Install the "backport-iwlwifi-dkms" package (sudo apt install 
backport-iwlwifi-dkms)
Unfortunately, the iwlwifi sources in this package are too old and only support 
pre-production AX210, so:
Grab the up-to-date backport-iwlwifi sources from Intel's github repository: 
git clone https://github.com/intel/backport-iwlwifi.git
Now go to /usr/src, there's a subdirectory with the old sources from step 1 
there (backport-iwlwifi-7906)
Copy the new sources to a new directory, e.g. sudo cp -a 
/whereever/you/cloned/to/backport-iwlwifi/iwlwifi-stack-dev 
backport-iwlwifi-8000
Copy the file "dkms.conf" from the old sources directory to the new sources 
directory and edit the second line to change the PACKAGE_VERSION from 7906 to 
8000
Remove the bad dkms module that was installed with the package in step 1: sudo 
dkms remove backport-iwlwifi/7906 --all
Add the updated dkms module with the version just created: sudo dkms add 
backport-iwlwifi/8000
Build and install the updated dkms modules: sudo dkms install 
backport-iwlwifi/8000
Now the driver is ready, but you still need to get the firmware for the chip:

Clone the linux-firmware repository: git clone 
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
Pick out the firmware files you need and copy them to /lib/firmware. If you're 
not sure which firmware you need, just boot with the new driver and check dmesg 
for messages from iwl: dmesg | grep iwl - the firmware files it was looking for 
will be named there.
PITFALL: The AX210 also needs an additional "pnvm" file, which is also found in 
the repository, but not quite well mentioned by the driver. If it is missing, 
it'll spray a ton of error messages.
For my Intel AX210 module, I ended up adding these files to /lib/firmware:

-rw-r--r-- 1 root root 1413868 Jun  3 18:27 iwlwifi-ty-a0-gf-a0-59.ucode
-rw-r--r-- 1 root root 1455104 Jun  3 18:27 iwlwifi-ty-a0-gf-a0-62.ucode
-rw-r--r-- 1 root root 1460012 Jun  3 18:27 iwlwifi-ty-a0-gf-a0-63.ucode
-rw-r--r-- 1 root root   27456 Jun  3 18:46 iwlwifi-ty-a0-gf-a0.pnvm
And it is up and running!

Bug#992790: Severity: High / Bug on Debian 11 Bullseye - Boot problem - Failed to start Load/Save RF Kill Switch Status

2021-08-28 Thread pham...@bluewin.ch

Hello,
After a clean reinstall the problem is persistent.
It is very difficult to use Debian 11 on a production machine due to this 
problem.
Debian 10 does not have this problem, but it seems to be present in some 
versions of Ubuntu.
It would have been wise to postpone the release of the final version in view of 
this very big bug...
Hope you will release a fix very soon, I cannot continue like this for x months.
Regards.
Philippe

Bug#992790: Severity: High / Bug on Debian 11 Bullseye - Boot problem - Failed to start Load/Save RF Kill Switch Status

2021-08-30 Thread pham...@bluewin.ch

Hello,
I found this post from another user who has the same issues as me...
https://unix.stackexchange.com/questions/665144/ufw-not-allowing-to-boot-debian-11/666854#666854
After reading it I'm wondering if this is a kernel or ufw issue.
Would a Debian expert be kind enough to advise me for this outage ?
Please note, systemd makes life a lot harder for me under Debian, I hope you 
will come back to Init soon !!!
Regards.
Philippe

Bug#985611: Debian 10 Buster - grub2 version 2.02+dfsg1-20+deb10u4

2021-03-20 Thread pham...@bluewin.ch

Package: grub2
Version: 2.02+dfsg1-20+deb10u4
 
Bug Description: Refused to start my Windows partition for a week
Error : no such devices : 4E2EA2552EA2363D
Load partition type to 0x83
error : invalide signature 
Best regards.
Philippe

Bug#985612: Debian 10 Buster - kernel version 4.19.0-14-amd64

2021-03-20 Thread pham...@bluewin.ch

Package: kernel 
Version: 4.19.0-14-amd64
Bug Description: My keyboard not work once in three when my machine starts => I 
have to restart it until my USB keyboard is finally recognized and I can enter 
my password to connect to my workstation ;-(
Best regards.
Philippe

Bug#985615: Debian 10 Buster - kernel version 4.19.0-14-amd64

2021-03-20 Thread pham...@bluewin.ch

Package: kernel 
Version: 4.19.0-14-amd64
Bug Description: My keyboard not work once in three when my machine starts => I 
have to restart it until my USB keyboard is finally recognized and I can enter 
my password to connect to my workstation ;-(
Best regards.
Philippe

Bug#986402: Debian 10 Buster - Kernel version 4.19.0-16-amd64 - USB keyboard not recognized at Debian login

2021-04-05 Thread pham...@bluewin.ch

Package: kernel 
Version: 4.19.0-16-amd64
Bug Description: My USB keyboard (Logitec Illumunate Keyboard / K740) is not 
recognized when I login (username / password) to Debian.
This problem only occurs if the keyboard is not used at boot when Grub 2 
displays the choice of OS and the automatic 10 seconds countdown is allowed to 
load Debian.
Consequence you have to restart your machine until you understand how to do it, 
so that your USB keyboard is recognized and that you can finally enter your 
username and password to connect to your PC ;-(
This bug occurs when the PC Bios is configured by default. If you change the 
following parameters then you can bypass it => USB configuration => Intel xHCI 
Mode => Smart Auto switched to > Auto or Enable.
Best regards.
Philippe

Bug#939579: Your software is still bugged !?!?

2021-04-05 Thread pham...@bluewin.ch

Hi,
It will soon be 1 year and a half that your software is bugged, would you be 
kind enough to do something to make it finally work correctly ? 
Regards.

Bug#939579: Your software is still bugged !?!?

2021-04-09 Thread pham...@bluewin.ch

Hello,
Not knowing what to do so that this bug that was present since the launch of 
Debian 10 is finally corrected, I wrote to you in these terms.
Gdebi crashes as soon as you ask it to install a package.
Choose a package, right click on, choose gdebi to do the job, then it crashes 
without installing your software
The MX Linux version of gdebi which was patched by the MX developer is working 
fine, if you want to ask him which patch he must have applied.
The Ubuntu version does not pose any problems either.
Imagine a new Debian user who does not know the commands to use in a terminal. 
If the software that is supposed to install the packages on its system doesn't 
work, what will it do? It is very bad publicity for Debian to leave such a big 
bug in the X-Windows environment. I don't understand that nothing has been done 
to fix this problem all this time.
Personally I am on Cinnamon but this bug affects all desktop environments from 
what I have read.
Effectively bug 932088 looks similar.
Please do something to correct this ASAP.
Regards.
Philippe

Bug#989777: Re: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

2021-08-15 Thread pham...@bluewin.ch

Hello,
Debian 11 Bullseye has been released, unfortunately it does not include a patch 
for the Intel AX210 Wifi & Bluetooth network adapter.
Unless you have a functional solution, I hope the Bullseye Backports directory 
will be created soon and propose the 5.13 kernel...
https://packages.debian.org/fr/linux-image-amd64
Regards.
Philippe

Bug#973524: Bug on Debian 10 Buster - xserver-xorg-video-nouveau (1:1.0.16-1)

2020-11-01 Thread pham...@bluewin.ch

Package: xserver-xorg-video-nouveau
Version: 1:1.0.16-1

Bug Description:
- My PC freezes-crash with the driver x after 15 to 45 minutes of use.
- The Debian 10 Buster "live-DVD" ISO image has been having problems for years. 
She freezes-crash @ reboot, due to bugs in the free Nvidia drivers.
Graphic card : Nvidia 750 Ti
Motherboard : Intel X99
Thank you for solve it with success.
Best regards.

Philippe

Bug#943758: Bug on Debian 10 Buster - Chromium 76.0.3809.100-1~deb10u1

2019-10-29 Thread pham...@bluewin.ch

Package: Chromium
 
 
  
 
 
  Version: 76.0.3809.100-1~deb10u1
 
 
  
 
 
  
 
 
   
 
 
  Bug Description:
 
 
  
 
 Chromium tells me after 10 minutes of use : 
Chromium version obsolete 
Can not update Chromium
Failed to install the latest version of Chromium
You do not have the latest features and security patches
 
   
 
 
  
 
 
  Best regards.
 
 
  
 
 
   
 
 
  Philippe

Bug#939545: Debian 10 Buster - Sound on 3.5 jack audio problem with Kernel v 4.19.0-5-amd64 (LTS)

2019-10-29 Thread pham...@bluewin.ch

Additional information:
As soon as I play music to listen to it the problem disappears. As soon as I
pause the music the problem reappears.
If I open the graphic tool "song settings" the problem stops. As soon as I
close it it reappears.
This problem is independent of the volume set by the user. Even with a volume
set to zero the problem is present.
The problem is present after the boot from the login window.
The problem is present with the computer connected to battery or 220 V sector
If I make a search on google with "dell xps 9570 ubuntu "noise" " argument :
https://www.google.com/search?q=dell+xps+9570+ubuntu+%22noise%22&ei=zcS2Xe6JFtSo8gKXhKbQBA&start=0&sa=N&ved=0ahUKEwiupNqj4b7lAhVUlFwKHReCCUo4ChDy0wMIlwE&biw=2558&bih=1273
I dont find a functional solution, but I realize that other users are impacted
by this problem.
The problem is very old, nobody solved it ;(
This post from 2014 talk about similar whistling in headphones
https://askubuntu.com/questions/457910/strange-noise-in-headphones-when-no-sound-is-played
The solution Below does not work well :
" Got the same problem on Dell XPS15 (9550, 2015 model in Xenial). Solved it in
alsamixer and muting the loopback channel.
$ alsamixer
Navigating to loopback (all the way to the right, with → key) and setting it to
Disabled using Mthe ↑ key. "
With Loopback Enable the whistling is his acute, with Loopback Disable the song
is low-pitched.
It seems clearly to be Realtek ALC3266 driver problem... all PCs equipped with
this sound card seem affected by this problem
Regards.
Philippe

Bug#944560: Bug on Debian 10 Buster - Kernel version 4.19.0-6-amd64

2019-11-11 Thread pham...@bluewin.ch

Package: Kernel
  
   
  
  
   Version: 4.19.0-6-amd64
   
  
  
   
  
  

  
  
   Bug Description:
  
  
   
  
  
When I connect my smartphone or my USB camera to my PC, the first time all 
works properly.
If I disconnect and reconnect it, it's impossible from this device to copy/cut 
and paste an image on my PC. My phone is a Sony Z5 Compact and my camera is an 
Canon Powershot G5x Mk II
  

  
  
   
  
  
   Best regards.
  
  
   
  
  

  
  
   Philippe

Bug#943758: Bug solved ok to close

2019-11-11 Thread pham...@bluewin.ch

Hello,
Bug solved with update today to version 78.0.3904.97 
Best regards.

Bug#944560: Bug on Debian 10 Buster - Kernel version 4.19.0-6-amd64

2019-11-12 Thread pham...@bluewin.ch

Post Scriptum :
I am forced to restart my PC to be able to have access again to the copy of 
files contained on my devices.
Best regards.
Philippe

Bug#939545:

2019-11-20 Thread pham...@bluewin.ch

Hello,
I have making tests in Debian 10, Mint 19.2 and Ubuntu 18.04, these 3 OS all 
suffer from the same problem with the priose 3.5mm jack that whistles when 
headphones are plugged in and no sound is broadcast.
The problem is related to the Realtek ALC3266 sound card.
If you open the sound settings software, the whistle disappears, as soon as you 
close the whistle comes back.
If you open VLC or any other player, the whistle disappears, as soon as you 
close it the whistle comes back.
When there is no signal sent to the sound card the problem is present.
One way to solve this problem would be to continuously send a "blank" signal 
(just a signal without sound) to this sound card.
After tests, this laptop works perfectly under Debian if it is connected to a 
"Sharkoon Gaming DAC Pro S (USB-DAC)" sound card or on a "USB-3 type C to 3.5 
mm jack adapter". But it does not work properly with the Realtek ALC3266 
integrated sound card.
Yesterday after I made an installation of MX Linux 19 on my laptop that does 
not use "systemd" but "init", I noticed that I have no problems with my 
headphones connected jack 3.5 mm to the Realtek ALC3266 integrated sound card 
 All work perfectly :) But I dont like realy this Linux distribution...
I hope that these additional indications will allow you to solve this bug which 
seems to exist since several years and has never been solved...
I hope that with a new look at this bug, that you finally will fix it !!!
Best regards.

Bug#939545: Fwd:

2019-11-20 Thread pham...@bluewin.ch

Post Scriptum :
 
MX Linux 19 OS with which everything is working properly is based on Debian 10 
Buster
 
  
 
 
  Best regards.

Bug#939545: Debian 10 Buster - Sound on 3.5 jack audio problem with Kernel v 4.19.0-5-amd64 (LTS)

2019-11-21 Thread pham...@bluewin.ch

Hello,
The origin of the problem was discovered.
This is a bug of powertop v.2.8-1 + b2.
By uninstalling software everything works except the energy saving of the 
battery of my laptop ;(
It's possible for you to make a urgent report for a urgent upgrade from 
powertop to the members Debian and Intel Team's development ??
The current version is 2.11 :
https://01.org/powertop/
And your versions is 2.10 on SID : 
https://packages.debian.org/search?keywords=powertop
If you need help for more details or tests feel free to send me an e-mail.
I dare to hope for a quick fix from you.
Best regards.
Philippe

Bug#945245: Powertop v.2.8-1 + b2

2019-11-21 Thread pham...@bluewin.ch

Package: powertop 
Version: v.2.8-1 + b2
Bug Description :
Unbearable whistling in headphones plugged into 3,5 mm audio jack port during 
the absence of broadcast (music/movie ended, paused, etc.)
My Dell XPS 9570 with the kernel  4.19.0-6-amd64 (LTS) are impacted by this bug 
;(
I have to use headphones the night for 3-4 hours to make no noise, it hurts my 
ears and this situation starts very seriously to exasperate me.
When I uninstalled powertop v.2.8-1 + b2 from Debian 10 all work fine... except 
the autonomy of my laptop ;(
!!! Powertop are installed automatically on all laptops powered by Debian !!! 
=> Many other users must also have this very unpleasant bug <=
Bug declared as coming from the kernel before good diagnosis :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939545
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939545#33
The current version of powertop is 2.11 :
https://01.org/powertop/
Your versions of powertop is v.2.8-1 + b2 in Buster and 2.10-1+b1 in SID : 
https://packages.debian.org/search?keywords=powertop
If you need help for more details or tests feel free to send me an e-mail.
I dare to hope for a quick/urgent fix from you.
Best regards.
Philippe

Bug#945245:

2019-11-21 Thread pham...@bluewin.ch

After installation-test of the SID powertop_2.10-1+b1_amd64 version, it's are 
also bugged.
The Unbearable whistling in headphones is always present.
It should quickly publish and test a version 2.11 hoping that the problem has 
been corrected with this version.
Regards.

Bug#939579: Debian 10 Buster - gdebi v. 0.9.5.7+nmu3

2019-11-24 Thread pham...@bluewin.ch

Hello,
The bug in this report has been fixed in the Linux MX 19 distribution (based on 
Debian 10) by applying a homemade patch :
gdebi 0.9.5.7+nmu3+mx19
https://distrowatch.com/table.php?distribution=mx&pkglist=true&version=19-beta1
https://mxlinux.org/
I tested Linux MX19, gdebi works perfectly on this distribution with their 
patch included, but not under native Debian 10 
You would be courteous to fix this bug in the next Debian update 10.3.
Best regards.
Philippe

Bug#940555: Debian 10 Buster - gnome logiciels (gnome softwares) v. 3.30.6

2019-09-17 Thread pham...@bluewin.ch

Package: gnome logiciels (gnome softwares)
Version: 3.30.6
  
Bug Description:   
Your software instalator (gnome logiciels v. 3.30.6) detects software and / or 
system updates but at the end of their installation he asks to reboot the 
machines while it is not necessary in most of the time.
After an update of a web browser a reboot is not necessary...
Since the kernel v. 4.x a reboot is not necessary in case of update of linux 
services, etc.
Your software also has a performance problem when searching for installed or 
installable packages, it is not able to list some of them. As it stands, it is 
much less efficient than Synaptic or the Linux Mint software manager.
It would be great if you develop a graphical driver manager like Mint and 
Ubuntu.
 Best regards.   Philippe

Bug#940702: Bug on Debian 10 Buster - Simple Scan v. 3.30.1.1

2019-09-19 Thread pham...@bluewin.ch

Package: Simple Scan
Version: 3.30.1.1

Bug Description:

"Simple Scan" software need 45 seconds for contact my Scanner Epson V300 Photo, 
every time when you start this program.
"Simple Scan" software everything worked perfectly under Debian 9. 
"Image Scan! for Linux" (v 2.30.2) need 55 second for starting every time when 
you run this program !?
Epson drivers version: iscan-gt-f720-bundle-1.0.1.x64.deb
This seems to be a problem related to Debian 10...
Best regards.

Philippe

Bug#940702: Bug on Debian 10 Buster - Simple Scan v. 3.30.1.1

2019-09-25 Thread pham...@bluewin.ch

Hello Jörg,
Thank you for your message.
I downloaded and installed the latest driver version 2.30.4 which was not 
available when I installed my Debian 10 Buster system.
Unfortunately the problem is the same with this new driver, the scanner puts 
between 50 seconds to a minute to initialize.
I have been using Linux Mint 1x.x (Ubuntu) for 15 years and on my laptop & 
workstation. I used only Linux Mint LMDE 2 and Linux Mint LMDE 3 (Debian) from 
4 years on my workstation.
I have never encountered such a problem before.
I'm not the only one having difficulty ... According to the articles I read the 
dependence LSB-CORE would be missing under Debian 10 which would pose many 
problems to users...
This does not seem to be a problem related to Epson drivers, but a change of 
dependencies within Debian 10 Buster that does not allow a perfect hardware 
backward compatibility with this hardware. I presume there is a bug in the new 
dependency used by Buster.
I hope that you can reopen this ticket and correct this bug...
Regards.
Philippe
https://www.debian-fr.org/search?q=lsb%20topic%3A79862
https://linuxdicasesuporte.blogspot.com/2019/07/multifuncional-epson-no-debian-10-buster.html

Bug#939545: Debian 10 Buster - Sound on 3.5 jack audio problem with Kernel v 4.19.0-5-amd64 (LTS)

2019-09-06 Thread pham...@bluewin.ch

Package: linux-image
Version: 4.19.0-5-amd64
Bug Description
Unbearable whistling in headphones plugged into 3,5 mm audio jack port during 
the absence of broadcast (music/movie ended, paused, etc.)
My Dell XPS 9570 with the kernel  4.19.0-5-amd64 (LTS) are impacted by this bug 
;(
I have to use headphones the night for 3-4 hours to make no noise, it hurts my 
ears and this situation starts very seriously to exasperate me.
Best regards.
Philippe

Bug#939579: Debian 10 Buster - gdebi v. 0.9.5.7+nmu3

2019-09-06 Thread pham...@bluewin.ch

Package: gdebi
Version: 0.9.5.7+nmu3
 
  Bug Description:
When you double click on .deb package gdebi start correctly but crash when you 
click on "install the package". 
Best regards.
Philippe

Bug#989777: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

2021-11-26 Thread pham...@bluewin.ch

Hello,
I am pleased to announce that bluetooth now works correctly with Kernel 
5.15.3-1: amd64 and my Intel AX210 Wifi / Bluetooth card :)
Keyboards on the other hand still cannot be paired, but this must be due to a 
Blueman v 2.1.4 dependency issue.
Unfortunately this Kernel still does not manage the switching between an Intel 
card (integrated) and Nvidia (discrete) on laptops.
Thank you for your support, this ticket can be closed.
Sincerely yours and a very happy New Year's Eve !!!
Best regards.
Philippe

Bug#989777: Fwd: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

2021-11-26 Thread pham...@bluewin.ch

P.S.It would be desirable for the users that this Kernel 5.15.3-1: amd64 
arrives quickly in the Backports section...
Regards.

Bug#1000703: Debian 11 - Blueman : Impossible to connect a bluetooth keyboard

2021-11-27 Thread pham...@bluewin.ch

 
Package: Blueman 
 
Version: 2.1.4-1+b1
 
Bug Description: Normally, during the pairing phase, a security PIN code must 
appear on the screen, then it must be entered on the keypad to confirm the 
correct choice of the device to be installed. This function does not work which 
makes pairing a keyboard or smartphone impossible ?! 
 
Please submit a fix.
 
Thank you by advance & regards.
 
Philippe

Bug#1000703: Debian 11 - Blueman : Impossible to connect a bluetooth keyboard

2021-11-27 Thread pham...@bluewin.ch

It is also impossible to pair the keyboard in command lines as described in the 
tutorial below :
https://wiki.debian.org/BluetoothUser
The pairing of mouse, headset and other equipment that does not require the 
introduction of a PIN code works without problem.
Regards.

Bug#1000700: Debian 11 - Cinnamon 4.8.6-2 dont work correctly

2021-11-28 Thread pham...@bluewin.ch

PS 
It would be nice for users that you integrate the choice of graphics card to 
use on a laptop (multi-GPU / Optimus, integrated or discrete card) when 
launching applications as proposed by Gnome.
Regards.

Bug#1000700: Debian 11 - Cinnamon 4.8.6-2 dont work correctly

2021-11-28 Thread pham...@bluewin.ch

Hello and thank you for your message,
- The desktop display bug is the most annoying, if you could fix it that would 
be great... I'm using a stable Debian, I'm afraid that if I upgrade Cinnamon 
with SID it created an unstable system for me.
- Having a small tool that allows you to choose between old style and new style 
would be so much more practical, in addition this tool exists in Linux Mint ...
   New users of Cinnamon under Debian or other OS (non Mint) do not even know 
that there is the option to choose between old and new style ;-(
   I know that in Debian very few people use Cinnamon yet, but this problem is 
also present in other Linux distributions that offer Cinnamon.
   This missing option therefore certainly affects more people than would 
appear in the first degree of analysis ...
- The choice of the GPU for laptop between integrated or discrete, at the 
launch of the programs, such as Gnome or Mate proposes it is absent from Debian 
11 + Cinnamon 4.8.6-2.  
I understand you, it is difficult to be in the oven and in the mill when you 
are working alone... From reading you, you seem to me to be an independent 
maintainer, not a developer of Cinnamon ?? 
Maybe you could ask the LMDE team at Cinnamon & Linux Mint to give you some 
help ? When I wrote to the Cinnamon development team about the 2nd issue (old 
style / new style), as a Debian user they tell us to contact you ;-(
We ended up wondering if it is not better to use Mate, XFCE or another desktop 
so as not to have any more problems on Debian...
Thank you for everything and have a good end of the weekend.

Bug#1000700: Debian 11 - Cinnamon 4.8.6-2 dont work correctly

2021-12-03 Thread pham...@bluewin.ch

Hello,
I don't speak English well either :)
- Yes, it is the folders on the desktop which change place after reboot and 
which do not align correctly and if I put a file on the desktop it overlaps the 
folders ;-(
- At this URL you can see the Mint configuration tool offering a traditional or 
modern desktop design. If we could have this module available under Debian that 
would be great. Ideally, this tool should be present in all distributions using 
Cinnamon...
https://sospc.name/wp-content/uploads/2019/02/L%E2%80%99%C3%A9cran-d%E2%80%99accueil-de-Linux-Mint-sospc.name-8.png
- I regret that there are not many people working on the project with you, I 
hope you will find some help.
Do what you can ... and close the ticket if you don't think you can do more.
Happy end of Year celebrations.
Philippe

Bug#1000700: Debian 11 - Cinnamon 4.8.6-2 dont work correctly

2021-12-04 Thread pham...@bluewin.ch

Hello,
- The problem with desktop folders occurs on my workstation + my laptop + a 
virtual machine that I created.
Changing the display settings included in Cinnamon does not resolve anything. 
See my settings as an attached file.
This happens on Debian 11 Bullseye Stable. Only one of the 10 installations I 
was able to do was functioning normally.
And after a reinstallation of Debian 11 on this machine without formatting the 
"/ home" the problem was also present on this machine there ;-(
- Yes, the tool is included in Mintwelcome which is present at LMDE and Mint 
20.x. Maybe the Mint team can help you by providing you with some code and 
helping you integrate it into Debian 11? For an informed user, configuring a 
Debian machine under Cinnamon with the old style results in a loss of a good 20 
minutes with each installation ;-( A beginner user will not be able to use the 
old style. With the tool included in Mintwelcome is instant...
Best regards.
Philippe

Bug#1000700: Debian 11 - Cinnamon 4.8.6-2 ne fonctionne pas correctement

2021-12-04 Thread pham...@bluewin.ch

Hello,
The problem exists on my computers with the "special icons" FWIK, as can be 
seen from the screenshots I have provided to you.
The auto-disposition function is not desirable for me, as it prevents manual 
positioning of folders.
I know I can retrieve the settings from /home, but a quick config tool would 
always be helpful, especially for people who don't know you can change styles 
or don't know how to change styles by hand. And then when you have problems 
like I described them to you, you think that your /home may be corrupted. In 
such a case you have to reconfigure everything by hand which takes a lot of 
time to know what to do before you get there... It would be desirable for such 
a tool to be present in the Cinnamon "System Settings" folder !!
Regards.
Philippe

Bug#989777: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

2021-10-11 Thread pham...@bluewin.ch

Hello Vincent,
I installed the 5.14.9-2 kernel: amd64 from testing.
After reboot I still have to install your old package for my wifi card to be 
detected :
https://snapshot.debian.org/archive/debian/20210313T203823Z/pool/non-free/f/firmware-nonfree/firmware-iwlwifi_20210208-4_all.deb
As with the 5.10 kernel there is only the Wifi which does not work and the 
Bluetooth ?!
I understood that Wifi worked from kernel 5.10 and Bluetooth worked from kernel 
5.10 ?!
Can you give me some good advice on how to get this damn Intel AX210 card 
working under Debian 11 Bullseye ??
Thanks in advance.
Meilleures salutations.
Philippe

Bug#989777: Re: Severity: High / Debian 10 &amp;amp; 11 with Kernel 5.10.x-amd64 =&amp;gt; Intel AX210 Wifi &amp;amp; Bluetooth not work

2021-10-14 Thread pham...@bluewin.ch

Hello Vincent,


Finally I had to force the installation of the firmware-iwlwifi 20210818-1 for 
it to work.

Configuring preferences.d (with files => stable-prioritaire + 
testing-on-bullseye) and sources.list  (see attached files) was not enough. By 
the way in Debian 12.1 sources.list is unusually short, it does not contain the 
"Bullseye base repository" or other directory, which can be very annoying for a 
beginner user...

After this manipulation the Bluetooth works +/-. When starting the OS for the 
first time, Bluetooth is present and working, I can connect my Logitech MX 
Anywhere 2S mouse but it is impossible to connect a Logitech CRAFT keyboard. 
Indeed, the Logitech CRAFT keyboard requires the entry of a series of numeric 
digits to confirm its connection with the OS, but no series of digits is 
provided by the OS to make this connection, so it fails...

After a simple start, the Bluetooth connection no longer works. If I try to 
start blueman-manager manually I get the following error message :


philippe@laptop:~$ blueman-manager
blueman-manager version 2.1.4 starting
blueman-manager 13.43.01 ERRORManager:118 on_dbus_name_appeared: Default 
adapter not found, trying first available.
blueman-manager 13.43.01 ERRORManager:122 on_dbus_name_appeared: No 
adapter(s) found, exiting


root@laptop:~# blueman-manager
Unable to init server: Could not connect: Connection refused
Unable to init server: Impossible de se connecter : Connection refused
Traceback (most recent call last):
  File "/usr/bin/blueman-manager", line 44, in 
manager = Blueman()
  File "/usr/lib/python3/dist-packages/blueman/main/Manager.py", line 29, in 
__init__
super().__init__(title=_("Bluetooth Devices"))
  File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 515, in 
__init__
raise RuntimeError(
RuntimeError: Gtk couldn't be initialized. Use Gtk.init_check() if you want to 
handle this case.


In this case if I run the command journalctl -k | grep -Ei 'bluetooth|iwlwifi' 
I get :


root@laptop:~# journalctl -k | grep -Ei 'bluetooth|iwlwifi' 
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: enabling device ( -> 
0002)
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: firmware: failed to load 
iwlwifi-ty-a0-gf-a0-64.ucode (-2)
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: Direct firmware load for 
iwlwifi-ty-a0-gf-a0-64.ucode failed with error -2
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: firmware: direct-loading 
firmware iwlwifi-ty-a0-gf-a0-63.ucode
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: api flags index 2 larger 
than supported by driver
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 0.0.2.25
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: loaded firmware version 
63.c04f3485.0 ty-a0-gf-a0-63.ucode op_mode iwlmvm
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
oct 14 13:34:21 laptop kernel: Bluetooth: Core ver 2.22
oct 14 13:34:21 laptop kernel: NET: Registered PF_BLUETOOTH protocol family
oct 14 13:34:21 laptop kernel: Bluetooth: HCI device and connection manager 
initialized
oct 14 13:34:21 laptop kernel: Bluetooth: HCI socket layer initialized
oct 14 13:34:21 laptop kernel: Bluetooth: L2CAP socket layer initialized
oct 14 13:34:21 laptop kernel: Bluetooth: SCO socket layer initialized
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware timestamp 2021.28 
buildtype 1 build 28502
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: No device address configured
oct 14 13:34:21 laptop kernel: bluetooth hci0: firmware: direct-loading 
firmware intel/ibt-0041-0041.sfi
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-0041-0041.sfi
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Boot Address: 0x100800
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware Version: 86-28.21
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware already loaded
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: Detected Intel(R) Wi-Fi 6 
AX210 160MHz, REV=0x420
oct 14 13:34:22 laptop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
oct 14 13:34:22 laptop kernel: Bluetooth: BNEP filters: protocol multicast
oct 14 13:34:22 laptop kernel: Bluetooth: BNEP socket layer initialized
oct 14 13:34:22 laptop kernel: iwlwifi :3b:00.0: firmware: direct-loading 
firmware iwlwifi-ty-a0-gf-a0.pnvm
oct 14 13:34:22 laptop kernel: iwlwifi :3b:00.0: loaded PNVM version 
0xd35929d8
oct 14 13:34:22 laptop kernel: iwlwifi :3b:00.0: Detected RF GF, 
rfid=0x10d000
oct 14 13:34:22 laptop kernel: iwlwifi :3b:00.0: base HW address: 
54:14:f3:52:7b:e1
oct 14 13:34:22 laptop kernel: iwlwifi :3b:00.0 wlp59s0: renamed from wlan0
oct 14 13:45:30 laptop kernel: iwlwifi :3b:00.0: Got NSS = 4 - trimming to 2


There is progress but it is not yet 100% functional...

Under Ubuntu everything works perfectly with the Kernel 5.11, but I hate using 
"sna

Bug#989777: Fwd: Re: Re: Severity: High / Debian 10 &amp;amp;amp; 11 with Kernel 5.10.x-amd64 =&amp;amp;gt; Intel AX210 Wifi &amp;amp;amp; Bluetooth not work

2021-10-14 Thread pham...@bluewin.ch

Small translation error :

After a simple start, the Bluetooth connection no longer works. If I try to 
start blueman-manager manually I get the following error message 

Correct translation :

After a simple reboot, the Bluetooth connection no longer works. If I try to 
start blueman-manager manually I get the following error message

 
Message d'origine
De : pham...@bluewin.ch
Date : 14/10/2021 - 14:11 (E)
À : vincent.deb...@free.fr
Cc : 989...@bugs.debian.org, andreimpope...@gmail.com, li...@packages.debian.org
Objet : Re: Re: Severity: High / Debian 10 &amp;amp;amp;amp; 11 with Kernel 
5.10.x-amd64 =&amp;amp;amp;gt; Intel AX210 Wifi &amp;amp;amp;amp; 
Bluetooth not work

Hello Vincent,


Finally I had to force the installation of the firmware-iwlwifi 20210818-1 for 
it to work.

Configuring preferences.d (with files => stable-prioritaire + 
testing-on-bullseye) and sources.list  (see attached files) was not enough. By 
the way in Debian 12.1 sources.list is unusually short, it does not contain the 
"Bullseye base repository" or other directory, which can be very annoying for a 
beginner user...

After this manipulation the Bluetooth works +/-. When starting the OS for the 
first time, Bluetooth is present and working, I can connect my Logitech MX 
Anywhere 2S mouse but it is impossible to connect a Logitech CRAFT keyboard. 
Indeed, the Logitech CRAFT keyboard requires the entry of a series of numeric 
digits to confirm its connection with the OS, but no series of digits is 
provided by the OS to make this connection, so it fails...

After a simple reboot, the Bluetooth connection no longer works. If I try to 
start blueman-manager manually I get the following error message :


philippe@laptop:~$ blueman-manager
blueman-manager version 2.1.4 starting
blueman-manager 13.43.01 ERRORManager:118 on_dbus_name_appeared: Default 
adapter not found, trying first available.
blueman-manager 13.43.01 ERRORManager:122 on_dbus_name_appeared: No 
adapter(s) found, exiting


root@laptop:~# blueman-manager
Unable to init server: Could not connect: Connection refused
Unable to init server: Impossible de se connecter : Connection refused
Traceback (most recent call last):
  File "/usr/bin/blueman-manager", line 44, in 
manager = Blueman()
  File "/usr/lib/python3/dist-packages/blueman/main/Manager.py", line 29, in 
__init__
super().__init__(title=_("Bluetooth Devices"))
  File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 515, in 
__init__
raise RuntimeError(
RuntimeError: Gtk couldn't be initialized. Use Gtk.init_check() if you want to 
handle this case.


In this case if I run the command journalctl -k | grep -Ei 'bluetooth|iwlwifi' 
I get :


root@laptop:~# journalctl -k | grep -Ei 'bluetooth|iwlwifi' 
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: enabling device ( -> 
0002)
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: firmware: failed to load 
iwlwifi-ty-a0-gf-a0-64.ucode (-2)
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: Direct firmware load for 
iwlwifi-ty-a0-gf-a0-64.ucode failed with error -2
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: firmware: direct-loading 
firmware iwlwifi-ty-a0-gf-a0-63.ucode
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: api flags index 2 larger 
than supported by driver
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: TLV_FW_FSEQ_VERSION: FSEQ 
Version: 0.0.2.25
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: loaded firmware version 
63.c04f3485.0 ty-a0-gf-a0-63.ucode op_mode iwlmvm
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: firmware: failed to load 
iwl-debug-yoyo.bin (-2)
oct 14 13:34:21 laptop kernel: Bluetooth: Core ver 2.22
oct 14 13:34:21 laptop kernel: NET: Registered PF_BLUETOOTH protocol family
oct 14 13:34:21 laptop kernel: Bluetooth: HCI device and connection manager 
initialized
oct 14 13:34:21 laptop kernel: Bluetooth: HCI socket layer initialized
oct 14 13:34:21 laptop kernel: Bluetooth: L2CAP socket layer initialized
oct 14 13:34:21 laptop kernel: Bluetooth: SCO socket layer initialized
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware timestamp 2021.28 
buildtype 1 build 28502
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: No device address configured
oct 14 13:34:21 laptop kernel: bluetooth hci0: firmware: direct-loading 
firmware intel/ibt-0041-0041.sfi
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Found device firmware: 
intel/ibt-0041-0041.sfi
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Boot Address: 0x100800
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware Version: 86-28.21
oct 14 13:34:21 laptop kernel: Bluetooth: hci0: Firmware already loaded
oct 14 13:34:21 laptop kernel: iwlwifi :3b:00.0: Detected Intel(R) Wi-Fi 6 
AX210 160MHz, REV=0x420
oct 14 13:34:22 laptop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
oct 14 13:34:22 laptop

Bug#989777: Re: Re: Bug#989777: Re: Severity: High / Debian 10 &amp;amp;amp;amp;amp;amp; 11 with Kernel 5.10.x-amd64 =&amp;amp;amp;amp;amp;gt; Intel AX210 Wifi &amp;amp;amp;amp

2021-10-22 Thread pham...@bluewin.ch

Good evening Vincent,

I am attaching 6 files to you with the commands you asked me to perform cold vs 
hot, hoping that this can help you to move things forward in the right 
direction.

On the Ubuntu side, version 21.04 with kernel 5.11 manages my Wifi / Bluetooth 
card perfectly, whether it is in "cold" or "hot" start-up. Wouldn't it be 
possible to integrate their work natively into Debian? It would be by far the 
easiest solution ... and they owe us that :)

Concerning the problem of the keyboard in Bluetooth, it must certainly come 
from a module missing in the dependencies of "Blueman" ... I have to see it 
more closely when I have a moment to devote to it.

Yes I am using a slightly customized version of Cinnamon as my desktop 
environment.

I saw that SID was in version 5.14.12-1: amd64 as soon as it goes into testing, 
I'll install it and get back to you. Hopefully this will solve my problem. What 
is the version of firmware-iwlwifi_xxx which is supplied with this kernel from 
SID ??

https://packages.debian.org/fr/linux-image-amd64

Have a nice weekend.

Philippe

PS : I can't answer you on your private messaging, your "Free.fr" provider must 
have a problem...



Message d'origine
De : vincent.deb...@free.fr
Date : 19/10/2021 - 17:59 (E)
À : pham...@bluewin.ch
Objet : Re: Re: Bug#989777: Re: Severity: High / Debian 10 
&amp;amp;amp;amp;amp; 11 with Kernel 5.10.x-amd64 =&amp;amp;amp;amp;gt; 
Intel AX210 Wifi &amp;amp;amp;amp;amp; Bluetooth not work

Le 2021-10-15 13:24, pham...@bluewin.ch a écrit :
> Hello Vincent,

Hi Philippe,

I'm sending this privately since I don't think the pairing issue is due to a
kernel issue.

> Thank you for your message.
 
You are welcome.
 
> Regarding the Kernel 5.14.0-2amd64 and the operation of Bluetooth with the 
> firmware-iwlwifi_20210818-1_all.deb, I confirm that at each cold start (power 
> OFF => power ON) the Bluetooth still works, but that each warm start (reboot) 
> the Bluetooth refuses to work.
 
Good to know. This confirms what I read here and there. It also shows that some
work is required for this driver to meet the expected stability.
 
> The 'solaar' package is very cool, I did not know him. 
> 
> Unfortunately it does not allow me to pair my keyboard in Bluetooth ;-( See 
> attached screenshots.

My bad, I misunderstood that you absolutely wanted to use bluetooth to
connect your keyboard to your system. Solaar does not handle connecting
or disconnecting via Bluetooth, which is done using the usual Bluetooth
mechanisms.
 
> I have the exact same problem with my workstation running Debian 11 with 
> kernel 5.10.0-9-amd64. 
> 
> It looks like a package is missing which has the role of displaying a numeric 
> code on the screen, which must then be entered on the keyboard to complete 
> safely the pairing of the keyboards ;-(

What desktop environment are you using? From the screenshots sent previously,
it looks like Cinnamon‽

Can you please show the output of the following commands?:

$ bluetoothctl show
# systemctl status bluetooth.service (as root)
 
> Best regards et bon week-end.
> 
> 
> Philippe

Bonne soirée,
Vincent





systemctl status bluetooth.service - Démarrage à froid
Description: Binary data


journalctl -k | grep -Ei 'bluetooth|iwlwifi' - Démarrage à froid
Description: Binary data


bluetoothctl show - Démarrage à froid
Description: Binary data


systemctl status bluetooth.service - Démarrage à chaud
Description: Binary data


journalctl -k | grep -Ei 'bluetooth|iwlwifi' - Démarrage à chaud
Description: Binary data


bluetoothctl show - Démarrage à chaud
Description: Binary data

Bug#989777: Severity: High / Debian 10 & 11 with Kernel 5.10.x-amd64 => Intel AX210 Wifi & Bluetooth not work

2021-10-25 Thread pham...@bluewin.ch

Hello,
I have tested the 5.14.9-2~bpo11+1: amd64 Kernel from Backports on my 
workstation, unfortunately it makes me lose compatibility with the Nvidia 
460.91.03 drivers.
Maybe DKMS was not activated when compiling these drivers ???
Best regards.
Philippe

Bug#1012216: Bug on Debian 11 Bullseye - systemd v.247.3-7

2022-06-01 Thread pham...@bluewin.ch

Package: systemd
Version: 247.3-7
Debian 11 64 Bits on Cinnamon desktop and kernel 5.17.3-1

Bug Description:

These errors appear in the boot log of my machine journalctl -b (journalctl -b)
jun 01 14:52:41 station systemd-xdg-autostart-generator[1827]: Exec binary 
'/usr/libexec/evolution-data-server/evolution-alarm-notify' does not exist: No 
such file or directory
jun 01 14:52:41 station systemd-xdg-autostart-generator[1827]: Not generating 
service for XDG autostart 
app-org.gnome.Evolution\x2dalarm\x2dnotify-autostart.service, error parsing 
Exec= line: No such file or directory
jun 01 14:52:41 station systemd-xdg-autostart-generator[1827]: Exec binary 
'/usr/lib/x86_64-linux-gnu/libexec/kdeconnectd' does not exist: No such file or 
directory
jun 01 14:52:41 station systemd-xdg-autostart-generator[1827]: Not generating 
service for XDG autostart app-org.kde.kdeconnect.daemon-autostart.service, 
error parsing Exec= line: No such file or directory
Debian 11 64 Bits on Cinnamon and kernel 5.17.3-1
Best regards.

Philippe

Bug#963170: Debian 10 Buster x64 - BlueZ: 5.50-1.2~deb10u1

2020-06-19 Thread pham...@bluewin.ch

Package: bluez 
Version: 5.50-1.2~deb10u1
Bug Description :
Hello, I'm would like to use my new bluetooth headphones Sony WH-1000XM3 on 
Linux Debian 10 Buster.
When I link it to my laptop everything works perfectly the first time. If I 
turn off this headset and I want to reuse it later, the connection is made but 
instead of being of good quality (A2DP Sink) it is done in SBS (HSP / HFP) 
which is of very poor quality. I am very unhappy with the result...
I'm on Debian 10 Buster x64 Bits, Desktop environment Cinnamon 3.8, BlueZ is on 
v. 5.50-1.2~deb10u1, blueman: 2.0.8-1
According to this information : 
https://github.com/blueman-project/blueman/issues/1209#issuecomment-626328772
BlueZ: 5.50-1.2~deb10u1 are the problem... Please add a 5.52 version to Sid and 
/ or to Backports. 
Best regards.

Bug#964188: chromium: high cpu load and frequent crashes

2020-07-10 Thread pham...@bluewin.ch

Hello,
The update is still not available for our PC's !?
In the last 10 minutes I just had 3 crashes of Chromium, it becomes really 
unbearable...
Can you deploy it please.
Regards.
Philippe

Bug#964188: Bug#964145: fixed in chromium 83.0.4103.116-1~deb10u2

2020-07-13 Thread pham...@bluewin.ch

Hello,
The bug is still present in Debian 10 Stable as well as in Raspbian OS designed 
from Debian 10 for Rappberry.
This bug was closed too early, no functional solution was deployed through the 
updates channel !?!?
The solution below of Riku is sorely lacking in detailed description and does 
not allow us, even manually, to correct this problem... 
In any case, thousands of PCs are certainly affected by this bug and there is a 
need to deploy a software update as soon as possible via the apt update, as not 
everyone is able to fix this manually and this problem is terribly annoying.
I hope you will do the necessary before the release of Debian 10.5 which is 
scheduled for July 18, 2020...
Debian is awesome but the problems seem to be sadly not taken care in a very 
thorough way of by the people who support it ;-( 
I also have a problem with Bluez and I need version 5.52 to fix it, but nothing 
is done to fix it ;-( What should i do for this ??
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963170
Best regards.
Philippe
This should fix it:
https://salsa.debian.org/chromium-team/chromium/-/commit/b904fa41d40b967dcc8f6984db52f7a2f6a2c83d
We are not building with GCC but this seems to be exactly the place where the 
crash happens.
chromium built with this patch has not crashed for the last few hours for me, 
while before it would
crash in a few minutes.
Riku

Bug#964188: Debian 10 Buster x64 - Chromium Version 83.0.4103.116 (Développement Build) built on Debian 10.4, running on Debian 10.4 (64 bits)

2020-07-03 Thread pham...@bluewin.ch

Package: Chromium 
Version: 83.0.4103.116 (Développement Build)
Bug Description :

Hello,

It's been 24 hours since Chromium was updated from the stable version to the 
Développement Build 83.0.4103.116 !?!?

This Développement Build is realy instable !!! 

There are regular crashes and very important slowness to open web pages !?!?!

A human error seems to be at the root of this problem...

Please correct this quickly... provide emergency a Stable Version for users, 
not a  Développement Build.

Thank you !!

Best regards.

Philippe

Bug#964188: chromium: crashes & system crashes after security update to v83

2020-07-04 Thread pham...@bluewin.ch

On Raspberry Pi 4 running with Raspbian 10 OS 64 bits (beta), the problem is 
the same, it is a developer version which was published and not a stable 
version.
Chrome is the official browser for Raspbian. It now takes 2 minutes 30 seconds 
to open the youtube.com page ;-( The only existing arm compatible alternative 
is Firefox.
Regards..

Bug#956135: blueman v. 2.0.8-1

2020-04-07 Thread pham...@bluewin.ch

Package: blueman 
Version: v. 2.0.8-1
Bug Description :
Hello, I'm using my new bluetooth headphones on Linux Debian 10 Buster (Sony 
WH-1000XM3).
When I link it to my laptop everything works perfectly the first time (although 
I unfortunately do not seem to benefit from the LDAC codec for which I bought 
this headset, it works satisfactorily in A2DP Sink). If I turn off this headset 
and I want to reuse it later, the connection is made but instead of being of 
good quality (A2DP Sink) it is done in SBS (HSP / HFP) which is of very poor 
quality. I am very unhappy with the result...
Is there a way to force the connection in A2DP Sink or to deactivate the codec 
SBS (HSP / HFP) which I do not use and thus to force the connection in A2DP 
mode Sink ? Is it possible to use the LDAC codec from Sony which is available 
for free for Android phones which is based on Linux ?
I'm on Debian 10 Buster x64 Bits, Desktop environment Cinnamon 3.8, BlueZ is on 
v. 5.50-1.2~deb10u1
Best regards.
Philippe

Bug#956203: Debian 10 Buster x64 - pulseaudio v. 12.2-4+deb10u1

2020-04-08 Thread pham...@bluewin.ch

Package: pulseaudio 
Version: v. 12.2-4+deb10u1
Bug Description :
Hello, I'm using my new bluetooth headphones on Linux Debian 10 Buster (Sony 
WH-1000XM3).
When I link it to my laptop everything works perfectly the first time (although 
I unfortunately do not seem to benefit from the LDAC codec for which I bought 
this headset, it works satisfactorily in A2DP Sink). If I turn off this headset 
and I want to reuse it later, the connection is made but instead of being of 
good quality (A2DP Sink) it is done in SBS (HSP / HFP) which is of very poor 
quality. I am very unhappy with the result...
Is there a way to force the connection in A2DP Sink or to deactivate the codec 
SBS (HSP / HFP) which I do not use and thus to force the connection in A2DP 
mode Sink ? Is it possible to use the LDAC codec from Sony which is available 
for free for Android phones which is based on Linux ?
I'm on Debian 10 Buster x64 Bits, Desktop environment Cinnamon 3.8, BlueZ is on 
v. 5.50-1.2~deb10u1, blueman: 2.0.8-1
Best regards.
Philippe

Bug#956135: blueman v. 2.0.8-1

2020-04-08 Thread pham...@bluewin.ch

Response obtained by Infirit, Blueman contributor on GitHub :
What codec is used it up to pulseaudio and blueman has no control over it. 
https://github.com/blueman-project/blueman/issues/1209
Regards.

Bug#945245: Powertop v.2.8-1 + b2 => Update to Powertop v. 2.11 from testing

2020-04-13 Thread pham...@bluewin.ch

Hello Kanru,
I saw your message a little late...
I just made a clean installation and add the testing repertory.
Unfortunately the result is the same, the hiss is still present in my 
headphones ;( But the installation is very stable for my. This is a perfect 
candidate to add it on backports repertory.
After this, if I add the backports repertory and install the Kernel v. 
5.4.0-0.bpo.4-amd64 after reboot => all is ok 
Powertop v. 2.11 with Kernel v. 5.4.0-0.bpo.4-amd64 solve the problem :)
Now I have a new problem :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956203
If you have a Idea for solve this, I will be very grateful to you.
Regards.
Philippe

Bug#939545: Debian 10 Buster - Sound on 3.5 jack audio problem with Kernel v 4.19.0-5-amd64 (LTS)

2020-04-13 Thread pham...@bluewin.ch

Problem is solved with Powertop v.2.11 from testing and Kernel 5.4 from 
backports.
Thank you very much for your work.
The ticket can be considered as resolved.
Powertop v.2.11 should be in backport, it works very fine !!!
Regards.
Philippe

Bug#956135: Please close the current ticket : #956135

2020-04-13 Thread pham...@bluewin.ch

Hello,
A new ticket is open for this problem :  #956203
Please close the current ticket : #956135
Thank you
Regards

Bug#944560: Bug on Debian 10 Buster - Kernel version 4.19.0-6-amd64

2020-04-15 Thread pham...@bluewin.ch

This bug is still present on kernel 4.19.0-8-amd64
See the attached screenshot for more details.
Regards.

Bug#940555: Debian 10 Buster - gnome logiciels (gnome softwares) v. 3.30.6

2020-04-17 Thread pham...@bluewin.ch

Hello, 
Persistent problem, unable to reach Gnome servers this time !?
Look at the attached screenshot...
Please offer us an update.
Thanks & regards.
Philippe

Bug#940555: RE: Bug#940555: Debian 10 Buster - gnome logiciels (gnome softwares) v. 3.30.6

2020-04-17 Thread pham...@bluewin.ch

I dont have problem with my connection internet connection,  all is ready for 
my.
Perhaps there is a problem with the servers contacted or with Gnome-Software, 
it is up to them to say...
Regards.
Message d'origine
De : magicman...@hotmail.com
Date : 17/04/2020 - 14:45 (E)
À : pham...@bluewin.ch, 940...@bugs.debian.org
Objet : RE: Bug#940555: Debian 10 Buster - gnome logiciels (gnome softwares) v. 
3.30.6
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin: 0.0in;
margin-bottom: 1.0E-4pt;
font-size: 11.0pt;
font-family: Calibri , sans-serif;
}
a:link, span.MsoHyperlink {
mso-style-priority: 99;
color: blue;
text-decoration: underline;
}
*.MsoChpDefault {
mso-style-type: export-only;
}
div.WordSection1 {
page: WordSection1;
}
 
Hi,
 
Have you checked your internet connection on there? It might be connection 
issues based on what it looks like.
 
  

  
 
Sent from  Mail for Windows 10

Bug#956203: Debian 10 Buster x64 - pulseaudio v. 12.2-4+deb10u1

According to this information :
https://github.com/blueman-project/blueman/issues/1209#issuecomment-626328772
BlueZ: 5.50-1.2~deb10u1 are the problem...
Please update BlueZ to the 5.51 version, for closing this ticket and to prevent 
other users from being stuck with this problem.
Best regards.

Bug#939579: Debian 10 Buster - gdebi v. 0.9.5.7+nmu3

Problem still not solved in Debian 10.4 ;-(
Please solve it to prevent other users from being stuck with this problem.
Regards.

Bug#940555: Please close the current ticket : #940555

Hello,
Please close the current ticket :  #940555
The problem is solved
Thank you
Regards

Bug#945245: A new version of Powertop 2.12 is available