Chamada para organizadores do Debian Day 2024 no Brasil
Olá, Estamos fazendo uma chamada para pessoas interessadas em organizar o Debian Day nas suas cidades para celebrar o 31o aniversário do Projeto Debian. Mais informações: https://debianbrasil.org.br/blog/debianday-brasil-2024-chamada-de-organizadores/ Abraços, -- Paulo Henrique de Lima Santana (phls) Belo Horizonte - Brasil Debian Developer Site: http://phls.com.br GPG ID: 0443C450 OpenPGP_signature.asc Description: OpenPGP digital signature
Re: [SOLVED] Re: Debian bookworm fails to install
Hi Hans! On Sat, Jun 08, 2024 at 11:43:38AM +0200, Hans wrote: > Hello! > > For those, who are interested in my discovering with bootcd, I attached a > screenshot of the > message, the installer told and why grub can not be installed. It might > explain more. > You might want to try OFTC IRC channel #debian-live or the debian-live or debian-boot mailing lists? All the very best, as ever, Andy (amaca...@debian.org)
[SOLVED] Re: Debian bookworm fails to install
Hello! For those, who are interested in my discovering with bootcd, I attached a screenshot of the message, the installer told and why grub can not be installed. It might explain more. However, I suppose, there are not many people in the world, building a live-system + installer + bootcd on it and want to install this. I believe, the package bootcd is only known by very few people at all. But as we are always want to improve things, I feel it important, to tell about this problem. As I said before: Dunno, whom I should file a bugreport! Anyway, take a look at the picture and you know more. For me, it looks like a dependency problem Have fun! Hans
Re: [SOLVED] Re: Debian bookworm fails to install
On Sat, 8 Jun 2024 11:45:49 +0700
Max Nikulin wrote:
Hello Max,
>On 08/06/2024 00:48, Hans wrote:
>> BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed
>No it does not. I have both installed. I think, the latter needs .mod
The pedant in me would point out that actually, no, you don't. Read that
second package name again. It doesn't exist.
Of course, I'm pretty certain that Hans typed the wrong thing and meant
to type 'grub-efi-amd64-signed'. No -bin-. From my (limited)
searching, it seems 'signed' & 'bin' are mutually exclusive in grub
package names and thus, if you have a '-signed' package, there must be a
corresponding '-bin' package installed for things to work.
Typographical mistakes are the main reason error messages, commands,
and what-not, should be copy/pasted in their entirety and not typed from
memory.
Remember:
Mistakes, like bad news, travel fast.
:-)
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
We don't need no-one to tell us what's right or wrong
The Modern World - The Jam
pgpBDcHX9UGs3.pgp
Description: OpenPGP digital signature
Re: [SOLVED] Re: Debian bookworm fails to install
On 08/06/2024 00:48, Hans wrote: BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed No it does not. I have both installed. I think, the latter needs .mod files provided by the former.
Re: [SOLVED] Re: Debian bookworm fails to install
On Fri, Jun 7, 2024 at 1:48 PM Hans wrote: > > Got it! Found the reason and a fix for it. > > Just not easy to find. It is an dependency-problem! > > What happened? > > Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul > exist in my live-system. During build this made no problems and all > dependencies are ok. But - during install it appears, that there is a > dependency conflict with the installer as bootcd needs grub-efi-amd64-bin. > > However, when bootcd wants to install, this package will be installed, too as > it is dependent. So far, so well. > > BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed > > and forces it to deinstall, > > which, you guess it, the debian-installer needs. > > And so the grub-installer crashes! > > Now the question, who should be asked for help? Maintainers of bootcd? > Maintainers of debian-installer? Or Maintainers of packages? > > I do not know, and as long as I do not know, I can not file a bugreport as > none of them (and this is fully correct and understandable) is responsible > from his sight on. > > However, the problem can easily be reproduced. Forgive my ignorance... How does this translate into an intermittent problem? It seems like you would never encounter it, or always encounter it. What makes the problem come and go? Jeff
Re: Debian bookworm fails to install
On Fri, Jun 7, 2024 at 3:08 PM Hans wrote: > > Hi folks, > > I am running into an issue, I can not explain. > > Let me please shortly describe: > > For my own purposes I am building a live-debian ISO with installer. As I am > finetuning some things (not related to the system itself), I am building > several ISOs a day. > > The live-build is set to bookworm (not bullseye, as lb config does). > > However, everything is going fine., the live-system is booting well. > > But: When I want to install it, the installer always breaks, when it wants to > install grub. (grub-installer fails). > > As I am doing always a fresh install with completely formatting the harddrive, > it can not be explained, why this happens. > > And more strange: When I build one version, it is working well. Changing > nothing, and building again, suddenly the installer crashes at grub > installation and then it will never work again. > > To declare: I can build several times, and every installation is working well, > and suddenly without any reason, it breakes. Doing then using one version > before (the last one, which worked well), it is still working, but the next > build is crashing. > > Ok, I think you understood, what I meant. Well, one reason I could imagine, > that the debian mirror, I add during installation process is changing. I am > using "deb.debian.org", but when using another mirror in my near, I am running > into the same issue. > > I also tried to install grub manually in the console during installation > process, using "grub-installer /target", but this did neither work nor show > much usefull information. > > Any idea, why this is happening? I saw similar messages in some forums, but > they are all related to Debian 10, which is rather old (and I suppose, these > bugs are fixed). You might have a look at grub2 bugs in Bookworm, and see if any look like they apply to you: <https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=grub2;dist=stable>. Jeff
Re: [SOLVED] Re: Debian bookworm fails to install
Looks like a typo from me. apt-cache search grub-efi-amd | grep signed grub-efi-amd64-signed - GRand Unified Bootloader, version 2 (amd64 UEFI signed by Debian) grub-efi-amd64-signed-template - GRand Unified Bootloader, Version 2 (Signaturvorlage für EFI-AMD64) It is grub-efi-amd64-signed. Sorry for that. I checked after install: If I want to install package bootcd after installation, no packages will be deinstalled, just several added. Not sure, what is the difference, between the installation process and the finished installation. Best Hans > > I can't find the package grub-efi-amd64-bin-signed. > Where should I look? > > Cheers, > David.
Re: [SOLVED] Re: Debian bookworm fails to install
On Fri 07 Jun 2024 at 19:48:21 (+0200), Hans wrote: > Got it! Found the reason and a fix for it. > Just not easy to find. It is an dependency-problem! > > What happened? > > Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul > exist in my live- > system. During build this made no problems and all dependencies are ok. But - > during install it > appears, that there is a dependency conflict with the installer as bootcd > needs grub-efi-amd64- > bin. > > However, when bootcd wants to install, this package will be installed, too as > it is dependent. So > far, so well. > BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed > and forces it to deinstall, > which, you guess it, the debian-installer needs. > > And so the grub-installer crashes! I can't find the package grub-efi-amd64-bin-signed. Where should I look? Cheers, David.
[SOLVED] Re: Debian bookworm fails to install
Got it! Found the reason and a fix for it. Just not easy to find. It is an dependency-problem! What happened? Well, in ~config/mylist.list.chroot I added the package "bootcd", which shoul exist in my live- system. During build this made no problems and all dependencies are ok. But - during install it appears, that there is a dependency conflict with the installer as bootcd needs grub-efi-amd64- bin. However, when bootcd wants to install, this package will be installed, too as it is dependent. So far, so well. BUT - grub-efi-amd64-bin conflicts with grub-efi-amd64-bin-signed and forces it to deinstall, which, you guess it, the debian-installer needs. And so the grub-installer crashes! Now the question, who should be asked for help? Maintainers of bootcd? Maintainers of debian- installer? Or Maintainers of packages? I do not know, and as long as I do not know, I can not file a bugreport as none of them (and this is fully correct and understandable) is responsible from his sight on. However, the problem can easily be reproduced. Thanks for reading this, hope it helps. For me, this issue can be closed. Best regards Hans
Re: Debian bookworm fails to install
Am Freitag, 7. Juni 2024, 18:24:11 CEST schrieb Michael Kjörling: Hi Michael, > On 7 Jun 2024 18:01 +0200, from hans.ullr...@loop.de (Hans): > > For my own purposes I am building a live-debian ISO with installer. > > How are you doing this? I am starting with lb config (to get a straight live-build environment). After this I am edititing all entries in ~/config/bootstrap | binary | common from "bullseye" to "bookworm". At last I am editing the entry for the name of the image from "live-image" to "RustDesk-live- image" (I want it so be named). Then lb config --purge. After this, I am starting with my own shell script, which contents this line: -------- ... lb config --purge lb config --debian-installer live --bootappend-live "boot=live username=myname hostname=my_hostname..." (keyboard definitions and so on) lb build This worked, but from one day to another no more, and this is strange! I also did a fresh live-build-environment installation, then it worked 3 or 4 times, and then it broke again. > > Can you post a script (or something similar) which reliably > demonstrates the issue when executed within a fresh Debian system? > The issue is not in the Debian itself, but it happens, when I want to install it. It happens as well on a native system as in Virtualbox itself. Maybe I could upload the ISO somewhere, it can be used in Virtualbox and shows the crash there, too. However, the ISO is 700MB and you need 8GB harddrive in Virtualbox. Think, not a goo idea. > > I also tried to install grub manually in the console during installation > > process, using "grub-installer /target", but this did neither work nor > > show > > much usefull information. > > Should we take this to mean that it did show _some_ "useful > information"? If so, what _did_ it show? No, it did not show any usefull information. Messages like "grub-installer failed" is no usefull information! No reason why... > > It appears that you are trying something; having some issue; see > symptoms; draw conclusions; and then tell us about your conclusions > and ask for a solution to your issue so as to be able to continue with > what you're trying to do. But without us being able to see what you > are doing and what happens when you do, _in full_, it's nearly > impossible to guess from your conclusions what might cause the issue > you're having in the first place. > Yeah, I know. If I got more information for myself, maybe I could find the reason for myself, too. But the installer does not show > Show us _exactly_ what's happening, as far as you are able. At a > minimum, make it easy for others to recreate a situation in which you > see the specific problem. > > In other words, a minimal (non)working example. At the moment, I try to use the installer from bullsyeye and the system of bookworm. It can be set in the live-build configurations. Maybe it is a problem with the debian-bookworm repo (mirroring in process, whatever) and tomorrow it will magiacally work again. So, I suppose, we should wait. I will try some things here and maybe I can fix it though. Thanks for help anyway. Best regards Hans
Re: Debian bookworm fails to install
On 7 Jun 2024 18:01 +0200, from hans.ullr...@loop.de (Hans): > For my own purposes I am building a live-debian ISO with installer. How are you doing this? Can you post a script (or something similar) which reliably demonstrates the issue when executed within a fresh Debian system? > I also tried to install grub manually in the console during installation > process, using "grub-installer /target", but this did neither work nor show > much usefull information. Should we take this to mean that it did show _some_ "useful information"? If so, what _did_ it show? It appears that you are trying something; having some issue; see symptoms; draw conclusions; and then tell us about your conclusions and ask for a solution to your issue so as to be able to continue with what you're trying to do. But without us being able to see what you are doing and what happens when you do, _in full_, it's nearly impossible to guess from your conclusions what might cause the issue you're having in the first place. Show us _exactly_ what's happening, as far as you are able. At a minimum, make it easy for others to recreate a situation in which you see the specific problem. In other words, a minimal (non)working example. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Debian bookworm fails to install
Hi folks, I am running into an issue, I can not explain. Let me please shortly describe: For my own purposes I am building a live-debian ISO with installer. As I am finetuning some things (not related to the system itself), I am building several ISOs a day. The live-build is set to bookworm (not bullseye, as lb config does). However, everything is going fine., the live-system is booting well. But: When I want to install it, the installer always breaks, when it wants to install grub. (grub-installer fails). As I am doing always a fresh install with completely formatting the harddrive, it can not be explained, why this happens. And more strange: When I build one version, it is working well. Changing nothing, and building again, suddenly the installer crashes at grub installation and then it will never work again. To declare: I can build several times, and every installation is working well, and suddenly without any reason, it breakes. Doing then using one version before (the last one, which worked well), it is still working, but the next build is crashing. Ok, I think you understood, what I meant. Well, one reason I could imagine, that the debian mirror, I add during installation process is changing. I am using "deb.debian.org", but when using another mirror in my near, I am running into the same issue. I also tried to install grub manually in the console during installation process, using "grub-installer /target", but this did neither work nor show much usefull information. Any idea, why this is happening? I saw similar messages in some forums, but they are all related to Debian 10, which is rather old (and I suppose, these bugs are fixed). Thanks for any hints and help! Best regards Hans
Re: Core files on Debian Trixie
Thomas Pircher wrote: I wanted to ask what the recommended way is nowadays to disable corefiles globally. The latest update for systemd has answered this: | apt-listchanges: News | - | | systemd (256~rc3-3) unstable; urgency=medium | | - coredumps are now disabled by default via configuration files rather than | an out-of-tree patch (installing the optional systemd-coredump package | will enable them as before). As always, overriding via local drop-ins is | possible if desired. The configuration files that respectively affect | the system systemd instance, the user systemd instances and PAM sessions | are: | | /usr/lib/systemd/system.conf.d/10-coredump-debian.conf | /usr/lib/systemd/user.conf.d/10-coredump-debian.conf | /usr/lib/sysctl.d/10-coredump-debian.conf | /etc/security/limits.d/10-coredump-debian.conf Thomas
Parenthesis or square brackets and "was" (was: Re: Monthly FAQ for Debian-user mailing list (last modified 20240501))
On 6/1/24 23:02, Max Nikulin wrote: On 02/06/2024 02:59, Andrew M.A. Cater wrote: If you change subject or emphasis in mid-thread, please change the subject line on your email accordingly so that this can be clearly seen. For example: New question [WAS Old topic] Are square brackets intentional here? E.g. thunderbird strips "(was:" subject part from response subject. This is true. I (on Thunderbird 115) had to restore the subject line after Thunderbird modified it. Do you know of a plugin or weird setting to make it stop doing that? Web searches were fruitless. -- A mob with torches and pitchforks approaches the castle. "Sire, the peasants are revolting!" "Yeah, disgusting, aren't they?"
Re: Help! secure boot is preventing boot of debian
"Thomas Schmitt" writes: > Hi, > > Richmond wrote: >> OK I got it booted and re-installed grub from debian. But I don't >> know why it happened, I haven't changed any keys or done anything >> except an opensuse update. I will ask the opensuse list > > I remember to have seen discussions about newly installed shim adding > names of older shims or bootloaders to something called SBAT. I find > in my mailbox a mail with a link to > https://bugzilla.opensuse.org/show_bug.cgi?id=1209985 > > About SBAT i found in the web: > > https://www.gnu.org/software/grub/manual/grub/html_node/Secure-Boot-Advanced-Targeting.html > https://github.com/rhboot/shim/blob/main/SBAT.md > > > Have a nice day :) > > Thomas Thanks. They have a wiki on how to fix this: https://en.opensuse.org/openSUSE:UEFI#Reset_SBAT_string_for_booting_to_old_shim_in_old_Leap_image I found re-installing debian's grub easier, until next time perhaps...
Re: Parenthesis or square brackets and "was" (was: Re: Monthly FAQ for Debian-user mailing list (last modified 20240501))
On Sun, Jun 02, 2024 at 10:02:58AM +0700, Max Nikulin wrote: > On 02/06/2024 02:59, Andrew M.A. Cater wrote: > > If you change subject > > or emphasis in mid-thread, please change the subject line on your email > > accordingly so that this can be clearly seen. > > > > For example: New question [WAS Old topic] > > Are square brackets intentional here? E.g. thunderbird strips "(was:" > subject part from response subject. Perhaps Gnus may treat square brackets > as well. I have no idea concerning other mailers. > No - the square brackets are an example :) Square brackets can be noticed, perhaps, and the effort to type them may be worth the distinctiveness, but what I really wanted was to make the distinction visually clear so that the reader would notice it.. I routinely type ammedments to the subject in square brackets and add WAS in upper case so that this is immediately apparent in a long email thread. Whatever your mailer does is fine but it needs to stand out clearly. Similarly, whenever I reply to something on behalf of the Community Team, I add that in square brackets to show that it is distinct. New topic - brackets or parentheses (WAS: Debian-user Monthly FAQ) might be appropriate here. So that email subjects don't go beyond 72 characters, you may always need to abbreviate the amended subject. [WAS: WAS: WAS (previous subject)] would be too many levels of off-topic discussion - but this discussion is still, just about, on topic. All the very best, as ever, Andy Cater (amaca...@debian.org) > Sorry for violating the rule. Curious users may test if their MUAs recognize > "(was: ...)" in the subject and remove old part. > > >
Re: Help! secure boot is preventing boot of debian
Hi, Richmond wrote: > OK I got it booted and re-installed grub from debian. But I don't know > why it happened, I haven't changed any keys or done anything except an > opensuse update. I will ask the opensuse list I remember to have seen discussions about newly installed shim adding names of older shims or bootloaders to something called SBAT. I find in my mailbox a mail with a link to https://bugzilla.opensuse.org/show_bug.cgi?id=1209985 About SBAT i found in the web: https://www.gnu.org/software/grub/manual/grub/html_node/Secure-Boot-Advanced-Targeting.html https://github.com/rhboot/shim/blob/main/SBAT.md Have a nice day :) Thomas
Re: Parenthesis or square brackets and "was" (was: Re: Monthly FAQ for Debian-user mailing list (last modified 20240501))
On Sun, Jun 02, 2024 at 10:02:58AM +0700, Max Nikulin wrote: > On 02/06/2024 02:59, Andrew M.A. Cater wrote: > > If you change subject > > or emphasis in mid-thread, please change the subject line on your email > > accordingly so that this can be clearly seen. > > > > For example: New question [WAS Old topic] > > Are square brackets intentional here? E.g. thunderbird strips "(was:" > subject part from response subject. Perhaps Gnus may treat square brackets > as well. I have no idea concerning other mailers. My despair and agony increase every time I hear about some new abomination that people's mail user agents perform by default. *face palms, shakes head*
Parenthesis or square brackets and "was" (was: Re: Monthly FAQ for Debian-user mailing list (last modified 20240501))
On 02/06/2024 02:59, Andrew M.A. Cater wrote: If you change subject or emphasis in mid-thread, please change the subject line on your email accordingly so that this can be clearly seen. For example: New question [WAS Old topic] Are square brackets intentional here? E.g. thunderbird strips "(was:" subject part from response subject. Perhaps Gnus may treat square brackets as well. I have no idea concerning other mailers. Sorry for violating the rule. Curious users may test if their MUAs recognize "(was: ...)" in the subject and remove old part.
Re: Help! secure boot is preventing boot of debian
Marco Moock writes: > Am 01.06.2024 um 20:01:43 Uhr schrieb Richmond: > >> Should I disable secure boot temporarily? will that allow booting? > > That should allow booting it. > > Have you changed anything at the keys in the EFI (maybe UEFI > firmware update)? OK I got it booted and re-installed grub from debian. But I don't know why it happened, I haven't changed any keys or done anything except an opensuse update. I will ask the opensuse list
Monthly FAQ for Debian-user mailing list (last modified 20240501)
Debian-user is a mailing list provided for support for Debian users, and to facilitate discussion on relevant topics. Codes of Conduct * The list is a Debian communication forum. As such, it is subject to both the Debian mailing list Code of Conduct and the main Debian Code of Conduct https://www.debian.org/MailingLists/#codeofconduct https://www.debian.org/code_of_conduct Guidelines for this list Some guidelines which may help explain how the list should work: Language * The language on this mailing list is English. There may be other mailing lists that are language-specific, for example, debian-user-french or debian-user-catalan * It is common for users to be redirected here from other lists, for example, from debian-project. It is also common for people to be posting here when English is not their primary language. Please be considerate. Answering questions and contributing to discussions constructively == * This is a fairly busy mailing list but even so you may have to wait some time for an answer - please be patient. * Help and advice on this list is provided by volunteers in their own time. It is common for there to be different opinions or answers provided. * It is not necessary to answer every post on the mailing list. * Be constructive in your responses. It may be that somebody else answers a question before you - if so, you should not reply simply in order to get the last word in, only reply if you can add useful information. Off-topic posts === * Please try to stay on topic. * Off-topic posts will happen occasionally as threads wander. Don't reply to them to make them carry on. * If you wish to introduce an off-topic subject that might be of interest to the wider list, start a new thread and preface the title with [OT]. * There is no debian-offtopic mailing list: please don't try to start one. Partisan topics and political arguments === * Arguments for the sake of it are not welcome here. * Partisan political / religious / cultural arguments do not belong here either. Debian's community is world wide; do not assume others will agree with your views or need to read them on a Debian list. Editing and answering mailing list posts * It is helpful to write meaningful subject lines. If you change subject or emphasis in mid-thread, please change the subject line on your email accordingly so that this can be clearly seen. For example: New question [WAS Old topic] * It may also be useful for someone to post a summary email from time to time to explain long threads. * Before posting, it may be useful to check your post for spelling mistakes and scan it for redundancy, duplicate words and redundancy. * Clear replies and a short mailing list thread are much easier to read and follow than long threads. * If you are replying to a post, please reply in-line if possible and cut out extra text that is not relevant to your point. Private replies and responding to posts off-list * Please post answers back to the list so others can benefit: private conversations don't benefit people who may only be following along on the list or reading the archives later. * We're only human: you may want to respond to someone off-list to make a point (or to wish them Happy Birthday / comment that you haven't seen them for a long time). We're also a community and the people you find on the list may become familiar friends BUT * Posting outside the list can be unhelpful: bad behaviour outside the lists can't easily be dealt with and will be invisible. You may inadvertently leak personal information by posting a private reply back to the list. If you *do* want to post outside the list - make it clear that you have done so at the top of the message. If someone replies to you privately and you think that this should go back to the list - ask them to post it to the list - do not just do so on their behalf without checking. I can't see what I want here - help me! === * It is often useful to look through the archives to see whether the issue you wish to raise or a similar issue has been raised before by someone else. The top level link to the archives of this list is at https://lists.debian.org/debian-user/ organised by year, then month. * Although there are only 20 or 30 regular contributors, there may be a couple of thousand readers in the background. Nobody is a mind reader, nobody can sit beside you. Please help by providing useful details if asked, especially which version of Debian you are running. I'm not using Debian but ... * Strictly, discussions of other distributions
Re: Help! secure boot is preventing boot of debian
Am 01.06.2024 um 20:01:43 Uhr schrieb Richmond: > Should I disable secure boot temporarily? will that allow booting? That should allow booting it. Have you changed anything at the keys in the EFI (maybe UEFI firmware update)? -- Gruß Marco Send unsolicited bulk mail to 1717264903mu...@cartoonies.org
Help! secure boot is preventing boot of debian
I have a PC with two operating systems installed, Debian, and Opensuse. Both are installed with Secure Boot. Each has its own grub installation. Normally I boot debian, and if I want to boot opensuse I select UEFI settings from the main menu and select opensuse from there which launches the opensuse grub. Today I booted opensuse, and did an update which included an update to grub. Now I cannot boot debian as it says bad shim or bad signature. Each grub menu has the alternate O.S. on it, but booting debian from the opensuse grub menu did not work either. Should I disable secure boot temporarily? will that allow booting?
Re: [solved] Re: No login with Debian 12 ssh client, ssh-rsa key, Debian 8 sshd
Just to compare, when Red Hat released 9.0 maybe 2 years ago (9.2 is current until 30 June) they disabled by default many older key-lengths and algorithms in SSL that were known to be weak. This caused issues for existing installations. You could either re-enable the weaker methods (easy but a pain to figure out courtesy of RH's layers of administration) or bite the bullet and re-key. On Sat, Jun 1, 2024, 5:51 AM Max Nikulin wrote: > On 01/06/2024 16:42, Thomas Schmitt wrote: > >debug1: Remote protocol version 2.0, remote software version > OpenSSH_6.7p1 Debian-5 > > > > (I wonder what the string "Debian-5" may mean. The Debian 12 machine has > > debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u2 > > So "-5" is not the Debian version. > > Package version in bookworm: 1:9.2p1-2+deb12u2 > >
Re: [solved] Re: No login with Debian 12 ssh client, ssh-rsa key, Debian 8 sshd
On 01/06/2024 16:42, Thomas Schmitt wrote: debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Debian-5 (I wonder what the string "Debian-5" may mean. The Debian 12 machine has debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u2 So "-5" is not the Debian version. Package version in bookworm: 1:9.2p1-2+deb12u2
[solved] Re: No login with Debian 12 ssh client, ssh-rsa key, Debian 8 sshd
Hi, Jeffrey Walton wrote: > If I am not mistaken, the problem you are experiencing is due to using > RSA/SHA-1 on the old machine. Max Nikulin wrote: > My reading of /usr/share/doc/openssh-client/NEWS.Debian.gz is that ssh-rsa > means SHA1 while clients offers SHA256 for the same id_rsa key. Indeed NEWS.Debian.gz links PubkeyAcceptedAlgorithms +ssh-rsa to RSA/SHA1. This is the explanation why the message does not say that ssh-rsa is disabled and why the web is so unclear about the ssh-rsa hash algorithm. So the Debian 12 client really offered the RSA key but not in a way the Debian 8 server could handle. The ssh -v messages have a line debug1: Remote protocol version 2.0, remote software version OpenSSH_6.7p1 Debian-5 (I wonder what the string "Debian-5" may mean. The Debian 12 machine has debug1: Local version string SSH-2.0-OpenSSH_9.2p1 Debian-2+deb12u2 So "-5" is not the Debian version. ) NEWS.Debian.gz says OpenSSH has supported RFC8332 RSA/SHA-256/512 signatures since release 7.2 and existing ssh-rsa keys will automatically use the stronger algorithm where possible. So the Debian 8 sshd is too old for a better ssh-rsa handshake and the connection might have been highjacked since 2022 "for
Re: No login with Debian 12 ssh client, ssh-rsa key, Debian 8 sshd
On 01/06/2024 01:52, Thomas Schmitt wrote: debug1: Offering public key:/home/.../.ssh/id_rsa RSA SHA256:... [...] The Debian 12 ssh client is obviously willing to try ssh-rsa. My reading of /usr/share/doc/openssh-client/NEWS.Debian.gz is that ssh-rsa means SHA1 while clients offers SHA256 for the same id_rsa key. * This release disables RSA signatures using the SHA-1 hash algorithm by default. This change has been made as the SHA-1 hash algorithm is cryptographically broken, and it is possible to create chosen-prefix hash collisions for
Re: No login with Debian 12 ssh client, ssh-rsa key, Debian 8 sshd
On Fri, May 31, 2024 at 7:08 PM Thomas Schmitt wrote: > > i still have network access to a Debian 8 system, to which i logged in > from Debian 11 via ssh and a ssh-rsa key. After the upgrade to Debian 12 > ssh fails with this public key authentication. > The probably relevant messages from a run of ssh -vvv are: > > debug1: Offering public key: /home/.../.ssh/id_rsa RSA SHA256:... > debug1: send_pubkey_test: no mutual signature algorithm > > To my luck, the old sshd already supports ssh-ed25519 and i was able to > add the content of the Debian 12 id_ed25519.pub to the Debian 8 file > .ssh/authorized_keys2 . Now ssh to the Debian 8 machine works again. > > But i find this error message "no mutual signature algorithm" strange. > The Debian 12 ssh client is obviously willing to try ssh-rsa. > The Debian 8 sshd accepted that key from Debian 11. Why not from 12 ? > > In > https://www.openssh.com/releasenotes.html > i find for 9.2 or older only a RequiredRSASize directive of which > man sshd_config says the default is 1024. > The ssh-rsa key was generated by Debian 10. man ssh-keygen of buster > says the default of option -b with RSA was 2048. > (Does anybody know how to analyze a key file in regard to such > parameters ?) If I am not mistaken, the problem you are experiencing is due to using RSA/SHA-1 on the old machine. The RSA modulus is large enough, but the hash is weak. That change happened at OpenSSH 8.9. `ssh -vvv` should show the ciphers offered by the server and client. It should look something like: debug2: KEX algorithms: curve25519-sha256,curve25519-sha...@libssh.org,e cdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,sntrup761x25519- sha...@openssh.com,diffie-hellman-group-exchange-sha256,diffie-hellman-g roup16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha25 6,ext-info-c,kex-strict-c-...@openssh.com debug2: host key algorithms: ssh-ed25519-cert-...@openssh.com,ecdsa-sha2 -nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com, ecdsa-sha2-nistp521-cert-...@openssh.com,sk-ssh-ed25519-cert-v01@openssh .com,sk-ecdsa-sha2-nistp256-cert-...@openssh.com,rsa-sha2-512-cert-v01@o penssh.com,rsa-sha2-256-cert-...@openssh.com,ssh-ed25519,ecdsa-sha2-nist p256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25...@openssh.com, sk-ecdsa-sha2-nistp...@openssh.com,rsa-sha2-512,rsa-sha2-256 Jeff
[solved] Re: No login with Debian 12 ssh client, ssh-rsa key, Debian 8 sshd
Hi, the following line in ~/.ssh/config did the trick: PubkeyAcceptedAlgorithms +ssh-rsa This lets ssh -v report: debug1: Offering public key: /home/.../.ssh/id_rsa RSA SHA256:... debug1: Server accepts key: /home/.../.ssh/id_rsa RSA SHA256:... Authenticated to ... ([...]:22) using "publickey". and leads to a shell session on the Debian 8 machine. So the mere message debug1: Offering public key: /home/.../.ssh/id_rsa RSA SHA256:... does not mean that RSA would be acceptable on the client side. It would be nice if the refusal message would be somewhat clearer than debug1: send_pubkey_test: no mutual signature algorithm I wrote: > > The ssh-rsa key was generated by Debian 10. man ssh-keygen of buster > > says the default of option -b with RSA was 2048. > > (Does anybody know how to analyze a key file in regard to such > > parameters ?) Michael Kjörling wrote: > $ ssh-keygen -l -f $pubkeyfile Says "2048 SHA256:... ...@... (RSA)". (Now that i know the right option, i can suddenly see it in the man page.) Have a nice day :) Thomas
Re: No login with Debian 12 ssh client, ssh-rsa key, Debian 8 sshd
On 31 May 2024 20:52 +0200, from scdbac...@gmx.net (Thomas Schmitt): > The ssh-rsa key was generated by Debian 10. man ssh-keygen of buster > says the default of option -b with RSA was 2048. > (Does anybody know how to analyze a key file in regard to such > parameters ?) $ ssh-keygen -l -f $pubkeyfile The first field of the output is the key length in bits (for RSA keys, this is the length of the modulus). -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
No login with Debian 12 ssh client, ssh-rsa key, Debian 8 sshd
Hi, i still have network access to a Debian 8 system, to which i logged in from Debian 11 via ssh and a ssh-rsa key. After the upgrade to Debian 12 ssh fails with this public key authentication. The probably relevant messages from a run of ssh -vvv are: debug1: Offering public key: /home/.../.ssh/id_rsa RSA SHA256:... debug1: send_pubkey_test: no mutual signature algorithm To my luck, the old sshd already supports ssh-ed25519 and i was able to add the content of the Debian 12 id_ed25519.pub to the Debian 8 file .ssh/authorized_keys2 . Now ssh to the Debian 8 machine works again. But i find this error message "no mutual signature algorithm" strange. The Debian 12 ssh client is obviously willing to try ssh-rsa. The Debian 8 sshd accepted that key from Debian 11. Why not from 12 ? In https://www.openssh.com/releasenotes.html i find for 9.2 or older only a RequiredRSASize directive of which man sshd_config says the default is 1024. The ssh-rsa key was generated by Debian 10. man ssh-keygen of buster says the default of option -b with RSA was 2048. (Does anybody know how to analyze a key file in regard to such parameters ?) In the web i find the reverse problem, i.e. older machine cannot ssh to Debian 12, because ssh-rsa would now be disabled by default. Have a nice day :) Thomas
Core files on Debian Trixie
Hi, I have noticed that started getting core files on Debian testing recently. I'm running a fairly standard installation with my own kernel build. I'm fine with this as default setting, but my knowledge in this area is probably outdated, so I wanted to ask what the recommended way is nowadays to disable corefiles globally. Should I change the settings in /etc/security/limits.d/ or set kernel.core_pattern in /etc/sysctl.d/? Just being curious, what package/change enabled this change? Thanks, Thomas
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hi Marc, On 20/05/24 at 14:35, Marc SCHAEFER wrote: 3. grub BOOT FAILS IF ANY LV HAS dm-integrity, EVEN IF NOT LINKED TO / if I reboot now, grub2 complains about rimage issues, clear the screen and then I am at the grub2 prompt. Booting is only possible with Debian rescue, disabling the dm-integrity on the above volume and rebooting. Note that you still can see the rimage/rmeta sub LVs (lvs -a), they are not deleted! (but no dm-integrity is activated). 4. update-grub GIVES WARNINGS Now, if I try to start update-grub while booted AND having enabled dm-integrity on the vg1/docker volume, I get: # update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.1.0-21-amd64 Found initrd image: /boot/initrd.img-6.1.0-21-amd64 error: unknown node 'docker_rimage_0'. [ ... many ... ] /usr/sbin/grub-probe: error: disk `lvmid/xLE0OV-wQy7-88H9-yKCz-4DUQ-Toce-h9rQvk/FzCf1C-95eB-7B0f-DSrF-t1pg-66qp-hmP3nZ' not found. error: unknown node 'docker_rimage_0'. [ ... many ... ] [ this repeats a few times ] Sorry for the late in the answer, but I've just noticed that the Linux kernel of Debian Bookworm ISO image (debian-12.0.0-amd64-DVD-1.iso) comes *without* "dm-integrity.ko" module, making therefore not possible to support volumes formatted with "--raidintegrity y" neither those formatted with "integritysetup" command (I think that it's a bug and it should be reported). When you booted in rescue mode which ISO image have you used? Thank for your patience, kind regards. -- Franco Martelli
Re: Continuous integration with Debian virtual machines
On Mon, 27 May 2024 10:00:02 +
André Rodier wrote:
Hello André,
>Anyone know a hosting service, like GitHub or GitLab, offering recent
>Debian
You asked, and were answered, yesterday. It would be preferable to
continue in that thread, rather than start a new one.
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
Hey there, Mr Average, you don't exist, you never did
Persons Unknown - Poison Girls
pgporAi1L4PrA.pgp
Description: OpenPGP digital signature
Continuous integration with Debian virtual machines
Dear Debian users, Anyone know a hosting service, like GitHub or GitLab, offering recent Debian virtual machines to run tests ? The last time I checked, they offered old Ubuntu versions or docker images, but I need a full Debian VM. For contextual information, the source code is here: https://github.com/progmaticltd/homebox My tests are relying on systemd services as well (so no docker), and some of them are pretty low-level. The packages names differences are big enough for the tests to fails, and I am not interested porting my solution to Ubuntu. Thanks for your insights. André Rodier.
Re: Continuous integration with Debian virtual machines
> Anyone know a hosting service, like GitHub or GitLab, offering recent Debian > virtual machines to run tests ? I'd expect most of them do, but at least SourceHut does according to https://man.sr.ht/builds.sr.ht/compatibility.md#debian Stefan
Re: Continuous integration with Debian virtual machines
On 26/5/24 18:35, André Rodier wrote: Dear Debian users, Anyone know a hosting service, like GitHub or GitLab, offering recent Debian virtual machines to run tests ? The last time I checked, they offered old Ubuntu versions or docker images, but I need a full Debian VM. For contextual information, the source code is here: https://github.com/progmaticltd/homebox My tests are relying on systemd services as well (so no docker), and some of them are pretty low-level. The packages names differences are big enough for the tests to fails, and I am not interested porting my solution to Ubuntu. Thanks for your insights. André Rodier. There are few options I can think of. VMWare Workstation Pro is now free for personal use so you can run recent Debian images as virtual machines in a Windows host (and linux host but YMMV). 8GB RAM is probably the minimum required. You also have the option of using native linux KVM. Going to the cloud hosting option, both AWS and Azure offer one year free tier options to run small virtual machines. They both have a large library of pre-configured systems that you can import and run including full Debian VM
Continuous integration with Debian virtual machines
Dear Debian users, Anyone know a hosting service, like GitHub or GitLab, offering recent Debian virtual machines to run tests ? The last time I checked, they offered old Ubuntu versions or docker images, but I need a full Debian VM. For contextual information, the source code is here: https://github.com/progmaticltd/homebox My tests are relying on systemd services as well (so no docker), and some of them are pretty low-level. The packages names differences are big enough for the tests to fails, and I am not interested porting my solution to Ubuntu. Thanks for your insights. André Rodier.
Re: Thunderbolt i debian 12: Thinkpad x390
Gràcies Laura per compartir tota aquesta recerca; a tu et servirà per a capejar un problema, i a altres ens servirà per a orientar-nos millor quan ens topem amb el Thundebolt. Llegeixo sobre temes de compatibilitat (cal saber segur de cada endoll USB-C si suporta Thunderbolt o no, i quines versions): «Some functionality may be available if a Thunderbolt device is connected to a USB-C port; this is implementation-dependent, and not guaranteed.» «Thunderbolt 4 supports Thunderbolt 3 devices, but not earlier versions. Thunderbolt 1 and 2 devices can be used with most, but not all, Thunderbolt 3 PCs with the use of an adapter.» «Thunderbolt 3 is a hardware interface developed by Intel. It shares USB-C connectors with USB, supports USB 3.1 Gen 2, and can require special "active" cables for maximum performance for cable lengths over 0.5 meters (1.5 feet).» De moment, la convergència no és completa amb USB, tot i què USB4 apunta maneres i en la majoria de casos admet dispositius Thunderbolt. El 24/5/24 a les 20:11, Laura Mora i Aubert ha escrit: Bona tarda, Obro un fil nou per a mostrar els veus avenços. Aprofito per explicar les coses que m'he anat trobant per a les persones que encara no heu tocat aquesta tecnologia. Spoiler: Era el cable, però tot i això no acaba d'anar del tot la cosa # BIOS Anem per la part més de ferro. A la BIOS, hi ha un apartat a config the és Thunderbolt (TM) 3. Atenció lu del numero és important. Thunderbolt 3 != Thunderbolt 4 (tot i que quan vaig comprar el cable dèia que Thunderbolt 4 també servia per Thunderbolt 3 i de moment sembla que no amb el què m'he trobat). Hi ha dues opcions que s'han de tenir en compte 1. Security Level: [No Security | User Authorization | Secure Connect | Diplay Port and USB] He definit "No Security", això fa que es validi automàticament Thunderbolt. Entenc que el boltctl serviria per autoritzar la connexió d'aquests dispositius. 2. Support in Pre Boot Environment, Thunderbolt (TM) Device: [Disabled| Enabled| Pre-Boot ACL] - Pre-OS support for Thunderbold devices attached to Thunderbolt 3 port. [Enabled] - Thunderbolt devices to be connected automatically [Pre-Boot ACL] - Thunderbolt devices to be connected after de the user authorization or automatically with security level "No Security" [Disabled] He provat les tres opcions, i no hi ha canvi. La que he deixat ara mateix és Pre-Boot ACL. Al arrancar la màquina he buscat alguna cosa de gestionar thunderbolt sense arrancar el sistema i no he vist cap opció. # UBUNTU He reiniciat i la ethernet seguia sense aparèixer. Així que he arrancat amb la liveCD d'ubuntu. Allà he anat a buscar thunderbolt i dintre d'opcions > security, allà hi era. Però no detectava la dock station. Se m'ha ocorregut canviar el cable per el que venia amb la dockstation que és massa curt i per a això vaig comprar-ne un de nou i dadá! la ethernet ha funcionat i ha detectat la dockstation però tampoc em deixava fer gran cosa. El cable que venia amb la dock és Thunderbolt 3 i el que vaig comprar Thunderbolt 4. He provat de canviar els cables un parell de cops i el 4 no l'hi agradava, en comptes el 3 si. El boltcl domains em detectava el domini actiu. He reiniciat a debian de nou i amb el cable Thunderbolt 3 la xarxa ha funcionat correctament. He buscat el nom de la interfície però no l'hi posa nom, sembla que ho fa directament des de la dock. Ni amb lspci ni amb lsusb, ni amb lshw veig el nom de la interfície root@triptofan:~# lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:16.3 Serial controller: Intel Corporation Cannon Point-LP Keyboard and Text (KT) Redirection (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #1 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel
Thunderbolt i debian 12: Thinkpad x390
Bona tarda, Obro un fil nou per a mostrar els veus avenços. Aprofito per explicar les coses que m'he anat trobant per a les persones que encara no heu tocat aquesta tecnologia. Spoiler: Era el cable, però tot i això no acaba d'anar del tot la cosa # BIOS Anem per la part més de ferro. A la BIOS, hi ha un apartat a config the és Thunderbolt (TM) 3. Atenció lu del numero és important. Thunderbolt 3 != Thunderbolt 4 (tot i que quan vaig comprar el cable dèia que Thunderbolt 4 també servia per Thunderbolt 3 i de moment sembla que no amb el què m'he trobat). Hi ha dues opcions que s'han de tenir en compte 1. Security Level: [No Security | User Authorization | Secure Connect | Diplay Port and USB] He definit "No Security", això fa que es validi automàticament Thunderbolt. Entenc que el boltctl serviria per autoritzar la connexió d'aquests dispositius. 2. Support in Pre Boot Environment, Thunderbolt (TM) Device: [Disabled| Enabled| Pre-Boot ACL] - Pre-OS support for Thunderbold devices attached to Thunderbolt 3 port. [Enabled] - Thunderbolt devices to be connected automatically [Pre-Boot ACL] - Thunderbolt devices to be connected after de the user authorization or automatically with security level "No Security" [Disabled] He provat les tres opcions, i no hi ha canvi. La que he deixat ara mateix és Pre-Boot ACL. Al arrancar la màquina he buscat alguna cosa de gestionar thunderbolt sense arrancar el sistema i no he vist cap opció. # UBUNTU He reiniciat i la ethernet seguia sense aparèixer. Així que he arrancat amb la liveCD d'ubuntu. Allà he anat a buscar thunderbolt i dintre d'opcions > security, allà hi era. Però no detectava la dock station. Se m'ha ocorregut canviar el cable per el que venia amb la dockstation que és massa curt i per a això vaig comprar-ne un de nou i dadá! la ethernet ha funcionat i ha detectat la dockstation però tampoc em deixava fer gran cosa. El cable que venia amb la dock és Thunderbolt 3 i el que vaig comprar Thunderbolt 4. He provat de canviar els cables un parell de cops i el 4 no l'hi agradava, en comptes el 3 si. El boltcl domains em detectava el domini actiu. He reiniciat a debian de nou i amb el cable Thunderbolt 3 la xarxa ha funcionat correctament. He buscat el nom de la interfície però no l'hi posa nom, sembla que ho fa directament des de la dock. Ni amb lspci ni amb lsusb, ni amb lshw veig el nom de la interfície root@triptofan:~# lspci 00:00.0 Host bridge: Intel Corporation Coffee Lake HOST and DRAM Controller (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP Thermal Controller (rev 30) 00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI Controller (rev 30) 00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 30) 00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi [Wireless-AC] (rev 30) 00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI Controller #1 (rev 30) 00:16.3 Serial controller: Intel Corporation Cannon Point-LP Keyboard and Text (KT) Redirection (rev 30) 00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #1 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #5 (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #9 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port #13 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 30) 00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 30) 00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 30) 00:1f.5 Serial bus controller: Intel Corporation Cannon Point-LP SPI Controller (rev 30) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-LM (rev 30) 01:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 root@triptofan:~# lsusb Bus 002 Device 008: ID 0951:1666 Kingston Technology DataTraveler 100 G3/G4/SE9 G2/50 Kyson Bus 002 Device 011: ID 17ef:3082 Lenovo ThinkPad TBT 3 Dock Bus 002 Device 010: ID 17ef:307f Lenovo USB3.1 Hub Bus 002 Device 009: ID 17ef:307f Lenovo USB3.1 Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b6d9 Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 2386:4338 Raydium Corporation Raydium Touch System Bus 001 Device 033: ID 2109:8887 VIA Labs, Inc. 40AN Bus 001 D
Re: Comment éditer un fichier .dwg sous Debian ?
- Mail original - De: "Olivier" À: "ML Debian User French" Envoyé: Jeudi 23 Mai 2024 13:03:37 Objet: Comment éditer un fichier .dwg sous Debian ? Bonjour, Il m'arrive d'échanger des données avec des architectes ou bureaux d'études qui publient des plans de bâtiment au format DWG d'AutoCAD. J'ai besoin d'ajouter des symboles (représentant des points d'accès WiFi) sur ces plans à partir de mon PC (j'en ai un sous Bullseye et un autre sous Bookworm) ou alternativement à l'aide d'un outil en ligne. Comment opérer ? Que conseillez-vous ? Slts Bonjour Olivier, En premier j'emploie Librecad pour dessiner et pour l'export en DWG, il me suffit d'employer un convertisseur qui est en paquet deb En premier, voici un début de piste : https://github.com/LibreDWG/libredwg la solution : https://www.opendesign.com/guestfiles/oda_file_converter le convertisseur qui sert de passerelle : https://download.opendesign.com/guestfiles/Demo/ODAFileConverter_QT6_lnxX64_8.3dll_25.4.deb Merci et bon courage pour la suite sincèrement Bernard Schoenacker Saverne Alsace
Re: Comment éditer un fichier .dwg sous Debian ?
Bonjour, Il m'arrive d'échanger des données avec des architectes ou bureaux d'études qui publient des plans de bâtiment au format DWG d'AutoCAD. J'ai besoin d'ajouter des symboles (représentant des points d'accès WiFi) sur ces plans à partir de mon PC (j'en ai un sous Bullseye et un autre sous Bookworm) ou alternativement à l'aide d'un outil en ligne. Comment opérer ? Que conseillez-vous ? Je n'ai pas d'expérience avec ce format, mais je sais que QGis peut ouvrir les différentes versions de ce format grâce à la bibliothèque GDAL. https://www.sigterritoires.fr/index.php/comment-integrer-des-donnees-dwg-dans-qgis/ https://gdal.org/drivers/vector/dwg.html N'hésite pas si tu as besoin sur l'installation et l'utilisation de QGis. Samy
Re: Comment éditer un fichier .dwg sous Debian ?
Bonjour, je n'ai jamais utilisé ce qui suit, mais la doc Freecad détaille les trois façons (modules externes: logiciel libre (à compiler), freeware (paquet Debian), logiciel commercial (40€)) dont ce logiciel peut importer des fichiers .dwg : https://wiki.freecad.org/index.php?title=FreeCAD_and_DWG_Import par curiosité, si tu tu peux donner des infos sur ce que tu as choisi et qui a marché ou non...
Re: Comment éditer un fichier .dwg sous Debian ?
J'ai essayé LibreCAD sur Bullseye et Bookworm avec respectivement des messages d'erreur définitive ou d'avertissement. Sur Bookworm, LibreCAD conseillait de convertir le fichier en DXF car "le support du DWG dans LibreCAD est incomplet". Je reste curieux vis à vis de retour d'expérience sur l'édition de fichier DWG. Le jeu. 23 mai 2024 à 15:28, Jean Bernon a écrit : > > librecad peut-être qui est dans les dépôts stable > > > > Bonjour, > > > > > > Il m'arrive d'échanger des données avec des architectes ou bureaux > > > d'études qui publient des plans de bâtiment au format DWG > > > d'AutoCAD. > > > > > > J'ai besoin d'ajouter des symboles (représentant des points d'accès > > > WiFi) sur ces plans à partir de mon PC (j'en ai un sous Bullseye et > > > un > > > autre sous Bookworm) ou alternativement à l'aide d'un outil en > > > ligne. > > > > > > Comment opérer ? Que conseillez-vous ? > > > > > > Slts > > > > > > Bonjour, > > > Peut-être avec librecad qui semble savoir ouvrir un dwg. > > > Salutations > > > -- > > Jack.R >
Re: Comment éditer un fichier .dwg sous Debian ?
librecad peut-être qui est dans les dépôts stable > > Bonjour, > > > > Il m'arrive d'échanger des données avec des architectes ou bureaux > > d'études qui publient des plans de bâtiment au format DWG > > d'AutoCAD. > > > > J'ai besoin d'ajouter des symboles (représentant des points d'accès > > WiFi) sur ces plans à partir de mon PC (j'en ai un sous Bullseye et > > un > > autre sous Bookworm) ou alternativement à l'aide d'un outil en > > ligne. > > > > Comment opérer ? Que conseillez-vous ? > > > > Slts > > > Bonjour, > Peut-être avec librecad qui semble savoir ouvrir un dwg. > Salutations > -- > Jack.R
Re: Comment éditer un fichier .dwg sous Debian ?
Le Thu, 23 May 2024 13:03:37 +0200, Olivier a écrit : > Bonjour, > > Il m'arrive d'échanger des données avec des architectes ou bureaux > d'études qui publient des plans de bâtiment au format DWG d'AutoCAD. > > J'ai besoin d'ajouter des symboles (représentant des points d'accès > WiFi) sur ces plans à partir de mon PC (j'en ai un sous Bullseye et un > autre sous Bookworm) ou alternativement à l'aide d'un outil en ligne. > > Comment opérer ? Que conseillez-vous ? > > Slts > Bonjour, Peut-être avec librecad qui semble savoir ouvrir un dwg. Salutations -- Jack.R
Comment éditer un fichier .dwg sous Debian ?
Bonjour, Il m'arrive d'échanger des données avec des architectes ou bureaux d'études qui publient des plans de bâtiment au format DWG d'AutoCAD. J'ai besoin d'ajouter des symboles (représentant des points d'accès WiFi) sur ces plans à partir de mon PC (j'en ai un sous Bullseye et un autre sous Bookworm) ou alternativement à l'aide d'un outil en ligne. Comment opérer ? Que conseillez-vous ? Slts
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 05:03:34PM -0400, Stefan Monnier wrote: > Hmm... I've been using a "plain old partition" for /boot (with > everything else in LVM) for "ever", originally because the boot loader > was not able to read LVM, and later out of habit. I was thinking of > finally moving /boot into an LV to make things simpler, but I see that > it'd still be playing with fire grub supports, for a long time: - / on LVM, with /boot within that filesystem - /boot on LVM, separately (it also worked with LILO, because LILO would record the exact address where the kernel & initrd was, regardless of abstractions layers :->) Recently, I have been playing with RAID-on-LVM (I was mostly using LVM on md before, which worked with grub), and it works too. Where grub fails, is if you have /boot on the same LVM volume group where any of the LVs "before him in order" have: - dm-integrity - specific metadata So yes, any advanced setup might break grub, and so the easiest is to have /boot on its separate partition again for the time being. Which makes two partitions of you also have an UEFI. > (AFAICT booting off of LVM was still not > supported by U-Boot either last time I checked). No idea about that one, sorry.
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
> I found this [1], quoting: "I'd also like to share an issue I've > discovered: if /boot's partition is a LV, then there must not be a > raidintegrity LV anywhere before that LV inside the same VG. Otherwise, > update-grub will show an error (disk `lvmid/.../...' not found) and GRUB > cannot boot. So it's best if you put /boot into its own VG. (PS: Errors > like unknown node '..._rimage_0 can be ignored.)" Hmm... I've been using a "plain old partition" for /boot (with everything else in LVM) for "ever", originally because the boot loader was not able to read LVM, and later out of habit. I was thinking of finally moving /boot into an LV to make things simpler, but I see that it'd still be playing with fire (AFAICT booting off of LVM was still not supported by U-Boot either last time I checked). Stefan
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 10:13:06AM +, Andy Smith wrote: > metadata tags to some PVs prevented grub from assembling them, grub is indeed very fragile if you use dm-integrity anywhere on any of your LVs on the same VG where /boot is (or at least if in the list of LVs, the dm-integrity protected ones come first). I guess it's a general problem how grub2 parses LVM, yes, as soon as their are special things going on, it somehow breaks. However, if you don't have /boot on LVM, hand-fixing grub2 can be trivial, e.g. here on another system with /boot/efi on 1st disk's first partition and /boot on 2nd disk's first partition. linux (hd1,1)vmlinuz-5.10.0-29-amd64 root=/dev/mapper/vg1-root ro quiet initrd (hd1,1)initrd.img-5.10.0-29-amd64 boot (you even have completions in grub's interactive boot system) and it boots. Next step: I am going to make me a USB boot key for that system, in case (first using a simple mount of two partitions of the USB key on /boot, respectively /boot/efi (vfat), then update-grub, or if it breaks, completely by hand like above -- I have been using syslinux for the last 20 years or so for that purpose, but it gets apparently too complicated with Secure Boot and stuff). PS: I have from now on decided I will always use a /boot no longer on LVM but on a separate partition, like the /boot/efi, it seems, indeed, much less fragile. Aka, back to what I was doing a few years ago before my confidence in grub2 got apparently too high :)
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 08:57:38AM +0200, Marc SCHAEFER wrote: > I will try this work-around and report back here. As I said, I can > live with /boot on RAID without dm-integrity, as long as the rest can be > dm-integrity+raid protected. I'm interested in how you get on. I don't (yet) use dm-integrity, but I have seen extreme fragility in grub with regard to LVM. For example, a colleague of mine recently lost 5 hours of their life (and their SLA budget) when simply adding metadata tags to some PVs prevented grub from assembling them, resulting in a hard to debug failed boot at next boot. Anything that involves grub having to interact with LVM just seems really fragile. Thanks, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Wed, May 22, 2024 at 08:57:38AM +0200, Marc SCHAEFER wrote: > I will try this work-around and report back here. As I said, I can > live with /boot on RAID without dm-integrity, as long as the rest can be > dm-integrity+raid protected. So, enable dm-integrity on all LVs, including /, /var/lib/lxc, /scratch and swap, now boots without any issue with grub2 as long as /boot is NOT on the same VG where the dm-integrity over LVM RAID is enabled. This is OK for me, I don't need /boot on dm-integrity. update-grub gives out warning for every of the rimage subvolumes, but can still then reboot. I would guess the bug is thus in grub2, not yet supporting boot on a /boot not necessarily dm-integrityfied itself, but on a VG where any of the LV is. Are readers seconding conclusion? If yes, I could report a bug on grub2. Have a nice day. Details: root@ds-03:~# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert docker vg1 rwi-aor--- 500.00g 100.00 [docker_rimage_0]vg1 gwi-aor--- 500.00g [docker_rimage_0_iorig] 100.00 [docker_rimage_0_imeta] vg1 ewi-ao <4.07g [docker_rimage_0_iorig] vg1 -wi-ao 500.00g [docker_rimage_1]vg1 gwi-aor--- 500.00g [docker_rimage_1_iorig] 100.00 [docker_rimage_1_imeta] vg1 ewi-ao <4.07g [docker_rimage_1_iorig] vg1 -wi-ao 500.00g [docker_rmeta_0] vg1 ewi-aor--- 4.00m [docker_rmeta_1] vg1 ewi-aor--- 4.00m root vg1 rwi-aor--- 10.00g 100.00 [root_rimage_0] vg1 gwi-aor--- 10.00g [root_rimage_0_iorig] 100.00 [root_rimage_0_imeta]vg1 ewi-ao 148.00m [root_rimage_0_iorig]vg1 -wi-ao 10.00g [root_rimage_1] vg1 gwi-aor--- 10.00g [root_rimage_1_iorig] 100.00 [root_rimage_1_imeta]vg1 ewi-ao 148.00m [root_rimage_1_iorig]vg1 -wi-ao 10.00g [root_rmeta_0] vg1 ewi-aor--- 4.00m [root_rmeta_1] vg1 ewi-aor--- 4.00m scratch vg1 rwi-aor--- 10.00g 100.00 [scratch_rimage_0] vg1 gwi-aor--- 10.00g [scratch_rimage_0_iorig] 100.00 [scratch_rimage_0_imeta] vg1 ewi-ao 148.00m [scratch_rimage_0_iorig] vg1 -wi-ao 10.00g [scratch_rimage_1] vg1 gwi-aor--- 10.00g [scratch_rimage_1_iorig] 100.00 [scratch_rimage_1_imeta] vg1 ewi-ao 148.00m [scratch_rimage_1_iorig] vg1 -wi-ao 10.00g [scratch_rmeta_0]vg1 ewi-aor--- 4.00m [scratch_rmeta_1]vg1 ewi-aor--- 4.00m swap vg1 rwi-aor--- 8.00g 100.00 [swap_rimage_0] vg1 gwi-aor--- 8.00g [swap_rimage_0_iorig] 100.00 [swap_rimage_0_imeta]vg1 ewi-ao 132.00m [swap_rimage_0_iorig]vg1 -wi-ao 8.00g [swap_rimage_1] vg1 gwi-aor--- 8.00g [swap_rimage_1_iorig] 100.00 [swap_rimage_1_imeta]vg1 ewi-ao 132.00m
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Additional info: On Wed, May 22, 2024 at 08:49:56AM +0200, Marc SCHAEFER wrote: > Having /boot on a LVM non enabled dm-integrity logical volume does not > work either, as soon as there is ANY LVM dm-integrity enabled logical > volume anywhere (even not linked to booting), grub2 complains (at boot > time or at update-grub) about the rimage LV. I found this [1], quoting: "I'd also like to share an issue I've discovered: if /boot's partition is a LV, then there must not be a raidintegrity LV anywhere before that LV inside the same VG. Otherwise, update-grub will show an error (disk `lvmid/.../...' not found) and GRUB cannot boot. So it's best if you put /boot into its own VG. (PS: Errors like unknown node '..._rimage_0 can be ignored.)" So, the work-around seems to be to simple have /boot not on a LVM VG where any LV has dm-integrity enabled. I will try this work-around and report back here. As I said, I can live with /boot on RAID without dm-integrity, as long as the rest can be dm-integrity+raid protected. [1] https://unix.stackexchange.com/questions/717763/lvm2-integrity-feature-breaks-lv-activation
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, On Tue, May 21, 2024 at 08:41:58PM +0200, Franco Martelli wrote: > I can only recommend you to read carefully the Wiki: > https://raid.wiki.kernel.org/index.php/Dm-integrity I did, and it looks it does not seem to document anything pertaining to my issue: 1) I don't use integritysetup (from LUKS), but LVM RAID PVs -- I don't use LUKS encryption anyway on that system 2) the issue is not the kernel not supporting it, because when the system is up, it works (I have done tests to destroy part of the underlying devices, they get detected and fixed correctly) 3) the issue is not with the initrd -- I added the dm-integrity module and rebuilt the initrd (and actually the bug happens before grub2 loads the kernel & init) -- or at least "not yet"! maybe this will fail later :) 4) actually the issue is just grub2, be it when the system is up (it complains about the special subvolumes) or at boot time Having /boot on a LVM non enabled dm-integrity logical volume does not work either, as soon as there is ANY LVM dm-integrity enabled logical volume anywhere (even not linked to booting), grub2 complains (at boot time or at update-grub) about the rimage LV.
Re: Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
On 20/05/24 at 14:35, Marc SCHAEFER wrote: Any idea what could be the problem? Any way to just make grub2 ignore the rimage (sub)volumes at setup and boot time? (I could live with / aka vg1/root not using dm-integrity, as long as the data/docker/etc volumes are integrity-protected) ? Or how to make grub 100% compatible with a vg1/root using dm-integrity (that would be obviously the final goal!) Thank you for any pointers! I can only recommend you to read carefully the Wiki: https://raid.wiki.kernel.org/index.php/Dm-integrity HTH kind regards -- Franco Martelli
Re: Sonido en Debian instalado en una Rpi4
El día 20/05/2024, a las 15:50, Camaleón escribió: > Parece un problema conocido relacionado con los controladores de audio > y/o el subsistema de gestión de sonido (PulseAudio/Jackd/ALSA, etc...). > > Mira a ver qué driver o stack de sonido instala/usa Raspberry Pi OS¹, > donde seguramente todo el hardware funcione sin problemas, y trata de > «emularlo» en Debian. > > ¹https://www.raspberrypi.com/software/operating-systems/ > > Gracias. Sí, creo que no me queda otro remedio. Me huelo que deberé recompilar el núcleo para añadir el módulo correspondiente.
Re: Sonido en Debian instalado en una Rpi4
El 2024-05-20 a las 11:49 +0200, Alfon escribió: > He seguido los pasos para instalar Debian descritos en: > https://wiki.debian.org/RaspberryPi4#Using_EFI_Firmware_and_the_regular_Debian_Installer > > Y todo ha ido bien, excepto que no tengo puedo usar la GPU para ver > vídeos con mpv y tampoco tengo sonido. Me interesa esto último, > ¿alguien lo ha conseguido? Parece un problema conocido relacionado con los controladores de audio y/o el subsistema de gestión de sonido (PulseAudio/Jackd/ALSA, etc...). Mira a ver qué driver o stack de sonido instala/usa Raspberry Pi OS¹, donde seguramente todo el hardware funcione sin problemas, y trata de «emularlo» en Debian. ¹https://www.raspberrypi.com/software/operating-systems/ Saludos, -- Camaleón
Debian bookwork / grub2 / LVM / RAID / dm-integrity fails to boot
Hello, 1. INITIAL SITUATION: WORKS (no dm-integrity at all) I have a Debian bookwork uptodate system that boots correctly with kernel 6.1.0-21-amd64. It is setup like this: - /dev/nvme1n1p1 is /boot/efi - /dev/nvme0n1p2 and /dev/nvme1n1p2 are the two LVM physical volumes - a volume group, vg1 is built with those PVs vg1 has a few LVs that have been created in RAID1 LVM mode: lvdisplay | egrep 'Path|Mirrored' LV Path/dev/vg1/root <-- this is / Mirrored volumes 2 LV Path/dev/vg1/swap Mirrored volumes 2 LV Path/dev/vg1/scratch Mirrored volumes 2 LV Path/dev/vg1/docker Mirrored volumes 2 As said, this boots without any issue. 2. ADDING dm-integrity WHILE BOOTED: works! Now, while booted, I can add dm-integrity to one of the volumes, let's say /dev/vg1/docker (this LV has absolutely no link with the boot process, except obviously it is listed in /etc/fstab -- it also fails the same way if even the swap is dm-integrit enabled, or /): lvconvert --raidintegrity y --raidintegritymode bitmap vg1/docker and wait a bit til the integrity is setup with lvs -a (100%) Obviously, this creates and uses a few rimage/rmeta sub LVs. Then I did this (after having boot issues): echo dm_integrity >> /etc/initramfs-tools/modules update-initramfs -u This did not change the below issue: 3. grub BOOT FAILS IF ANY LV HAS dm-integrity, EVEN IF NOT LINKED TO / if I reboot now, grub2 complains about rimage issues, clear the screen and then I am at the grub2 prompt. Booting is only possible with Debian rescue, disabling the dm-integrity on the above volume and rebooting. Note that you still can see the rimage/rmeta sub LVs (lvs -a), they are not deleted! (but no dm-integrity is activated). 4. update-grub GIVES WARNINGS Now, if I try to start update-grub while booted AND having enabled dm-integrity on the vg1/docker volume, I get: # update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-6.1.0-21-amd64 Found initrd image: /boot/initrd.img-6.1.0-21-amd64 error: unknown node 'docker_rimage_0'. [ ... many ... ] /usr/sbin/grub-probe: error: disk `lvmid/xLE0OV-wQy7-88H9-yKCz-4DUQ-Toce-h9rQvk/FzCf1C-95eB-7B0f-DSrF-t1pg-66qp-hmP3nZ' not found. error: unknown node 'docker_rimage_0'. [ ... many ... ] [ this repeats a few times ] Found linux image: /boot/vmlinuz-6.1.0-10-amd64 Found initrd image: /boot/initrd.img-6.1.0-10-amd64 Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi Warning: os-prober will not be executed to detect other bootable partitions. [ there are none ] Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. Adding boot menu entry for UEFI Firmware Settings ... done Any idea what could be the problem? Any way to just make grub2 ignore the rimage (sub)volumes at setup and boot time? (I could live with / aka vg1/root not using dm-integrity, as long as the data/docker/etc volumes are integrity-protected) ? Or how to make grub 100% compatible with a vg1/root using dm-integrity (that would be obviously the final goal!) Thank you for any pointers!
Re: Debian, fail2ban, Version?
On 20 May 2024 07:00 -0400, from d...@randomstring.org (Dan Ritter): >> # fail2ban-server -V >> >> 0.11.2 > > Bullseye became stable in August of 2021. It's also perhaps worth noting that there seem to have been only two interim releases. https://github.com/fail2ban/fail2ban/releases lists 0.11.2 (Nov 2020), 1.0.1 (Sep 2022), 1.0.2 (Nov 2022) and 1.1.0 (April 2024). The release notes for 1.1.0 says 0.11 or 1.0 can be used if you have Python < 3.5; and 1.0.1 says 0.11 can be used if you have Python < 2.7. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: Debian, fail2ban, Version?
Maurizio Caloro wrote: > Hello > > Please why on Debian Bullseye, 11.9 is a pretty old version available in the > repository? > > # fail2ban-server -V > > 0.11.2 Bullseye became stable in August of 2021. "Stable" means that packages don't change except to fix serious bugs, especially security-related bugs. Bookworm became stable in June of 2023. The fail2ban version there is 1.0.2-2. -dsr-
Debian, fail2ban, Version?
Hello Please why on Debian Bullseye, 11.9 is a pretty old version available in the repository? # fail2ban-server -V 0.11.2 I think this application arnt a big thing? Available on github, Version 1.1.0
Sonido en Debian instalado en una Rpi4
Hola lista, He seguido los pasos para instalar Debian descritos en: https://wiki.debian.org/RaspberryPi4#Using_EFI_Firmware_and_the_regular_Debian_Installer Y todo ha ido bien, excepto que no tengo puedo usar la GPU para ver vídeos con mpv y tampoco tengo sonido. Me interesa esto último, ¿alguien lo ha conseguido? Saludos.
Re: Regression in Radeon driver in latest Debian Stable kernel
On 17 May 2024 00:12 +0700, from maniku...@gmail.com (Max Nikulin): > Be realistic, to get the bug fixed, there should be affected persons > motivated enough to try vanilla kernel or even to build custom kernels with > provided patches. Developers time is limited and expensive resource. It may > be directed to fixing other bugs. If you can compare Debian and upstream > kernels you may get the issue fixed quicker. Direct communication with > driver developers may be more effective. Indeed; that's why I suggested trying the vanilla kernels of the same versions, compiled with the same options, and seeing if the behavior can be reproduced with those. If the same behavior as seen with the Debian-packaged kernels can be reproduced with the vanilla kernel, that would very strongly suggest that whatever this is is either (a) an upstream issue in the kernel, or (b) not a kernel issue at all. There's a reason why many upstream maintainers, when faced with a bug report for a downstream potentially modified version of their code, will start by saying "try our version". Adding to the "be realistic", if the issue was an obvious one, it likely never would have made it into a released kernel at all. So whatever this is about is unlikely to be obvious. Thus some detective work is most likely going to be needed; and unless a kernel developer can reproduce the problem on their own hardware, they'll probably have to ask you to try things out and report back; whether with debug logs, more detailed system information, or as Max mentioned building a kernel with a proposed fix to see what effect, if any, a proposed fix has on the problem. Also, especially if you start installing backports kernels as well, you may want to add a version pin to the kernel you currently have installed and which does not exhibit the problem to the same degree, to reduce the risk that it gets purged for being among the older ones you have installed. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Re: Regression in Radeon driver in latest Debian Stable kernel
On 16/05/2024 22:53, piorunz wrote: https://bugzilla.kernel.org/ will they be interested in Debian specific error? I don't use vanilla kernel so maybe it's Debian only problem. If you *find* a similar report there then it is likely an upstream issue. (Developers of specific driver may use another bug tracker.) Do you have a recipe how to trigger the bug? Otherwise it may be much harder to fix it. Be realistic, to get the bug fixed, there should be affected persons motivated enough to try vanilla kernel or even to build custom kernels with provided patches. Developers time is limited and expensive resource. It may be directed to fixing other bugs. If you can compare Debian and upstream kernels you may get the issue fixed quicker. Direct communication with driver developers may be more effective.
Re: How to create a custom Debian ISO
Hi, Aditya Garg wrote: > This one is gonna be interesting. > Wish me luck. Fingers are crossed ... (But everything in the procedure is supposed to be deterministic. So there is few room for luck, good or bad. We rather have to navigate the chaos.) Have a nice day :) Thomas
Re: How to create a custom Debian ISO
Well I'm used to unsquashfs, chroot, squashfs and repack the iso. This one is gonna be interesting. Wish me luck. > On 16 May 2024, at 9:42 PM, Thomas Schmitt wrote: > > Hi, > > to...@tuxteam.de wrote: >> Not the OP, but thanks, Thomas. > > Well, ISO 9660 is known to be my hobby. So i can hardly resist trying > to acquire new users for xorriso. > > > Have a nice day :) > > Thomas >
Re: How to create a custom Debian ISO
Hi, to...@tuxteam.de wrote: > Not the OP, but thanks, Thomas. Well, ISO 9660 is known to be my hobby. So i can hardly resist trying to acquire new users for xorriso. Have a nice day :) Thomas
Re: Regression in Radeon driver in latest Debian Stable kernel
On 16/05/2024 12:35, Max Nikulin wrote: On 16/05/2024 17:35, piorunz wrote: As much as I would like to try vanilla kernel, I don't want to break my system. I use Debian Stable, don't know if things would just work with vanilla kernel. You may try bookworm-backports kernel 6.6.13+bpo-amd64 You may check https://bugzilla.kernel.org/ for reports similar to your one. Oh that's great solution, I will try that without risk of breaking my system, as I always can select previous kernel in the menu, thank you. https://bugzilla.kernel.org/ will they be interested in Debian specific error? I don't use vanilla kernel so maybe it's Debian only problem. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: How to create a custom Debian ISO
On Thu, May 16, 2024 at 05:20:40PM +0200, Thomas Schmitt wrote: > Hi, > > Aditya Garg wrote: > > I would prefer making the ISO as similar to the official Debian ISO and just > > replace the Debian kernel with the customised kernel. > > In that case, i'd go along [...] Not the OP, but thanks, Thomas. Your posts are always a trove. And pleasant, on top! Cheers -- t signature.asc Description: PGP signature
Re: How to create a custom Debian ISO
Hi, Aditya Garg wrote: > I would prefer making the ISO as similar to the official Debian ISO and just > replace the Debian kernel with the customised kernel. In that case, i'd go along https://wiki.debian.org/RepackBootableISO Either by using the xorrisofs options in /.disk/mkisofs of the ISO : https://wiki.debian.org/RepackBootableISO#Learn_about_the_actually_used_ISO_production_command or by relying on the capability of xorriso to determine the commands which will reproduce the boot equipmemt of the loaded ISO : https://wiki.debian.org/RepackBootableISO#In_xorriso_load_ISO_tree_and_write_modified_new_ISO If you need help with finding the appropriate xorriso commands, ask me in private or in public at bug-xorr...@gnu.org . What remains is to find out whether this works out of the box or whether the kernel has to be announced in some files of the ISO or even cryptographically signed in some way. -- Just in case your adventure goes beyond replacing the kernel and possibly the boot loader menu files, i warn of a bug in xorriso-1.5.6 and older: Don't overwrite the El Torito boot image files in a xorriso run that uses -boot_image "any" "replay" The boot image files in Debian amd64 ISOs are /isolinux/isolinux.bin and /boot/grub/efi.img . If you need to replace them, then we have to talk. Have a nice day :) Thomas
Re: How to create a custom Debian ISO
Well it's indeed not as easy as I thought as far as Debian ISOs are concerned. I'll try to be more precise. I am a maintainer for Ubuntu on Linux on T2 Macs project: https://t2linux.org/. We work to modify ISOs of commonly used distros by adding a custom kernel with drivers for T2 Macs and provide to the users. There has been a demand for Debian for a long time and I wish to provide the ISOs for the same. I would prefer making the ISO as similar to the official Debian ISO and just replace the Debian kernel with the customised kernel. I've already set up an apt repo which hosts the kernels over here: https://github.com/AdityaGarg8/t2-ubuntu-repo I'll be thankful if I get the best possible option. On 11 May 2024, at 8:33 PM, Thomas Schmitt wrote: Hi, Aditya Garg wrote to debian-devel: I wanted to create a custom ISO of Debian, with the following customisations: 1. I want to add a custom kernel that supports my Hardware. 2. I want to add my own Apt repo which hosts various software packages to support my hardware. I am not able to get any good documentation for the same. Please help. Marvin Renich wrote: The package live-build from the Debian Live project might help you do what you want. Indeed the live-build package seems to be in use outside Debian's own ISO production. Mailing list is debian-l...@lists.debian.org There exists a manual https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html Installation ISOs are made by package debian-cd, of which i am not aware that it would have have users outside the official ISO production.i Mailing list is debian...@lists.debian.org Your impression about lack of documentation is not wrong as far as this project is concerned. :)) Nevertheless the production step of packing up the ISO from a prepared file tree is documented together with methods to use a Debian installation ISO as base for the preparation: https://wiki.debian.org/RepackBootableISO Packages may probably be added at the appropriate place in the directory tree under /pool. (Managing a Debian repo is not my turf. Sorry for being vague here.) Changing the content of a Debian ISO might need some follow-up work in administrative files of the ISO. When merging Debian ISOs, my script https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos manipulates: /README.txt /dists/*/Release and merges the files listed in /dists/*/Release. You would have to explore whether these files are affected by your changes. Have a nice day :) Thomas
Re: Regression in Radeon driver in latest Debian Stable kernel
On 16/05/2024 17:35, piorunz wrote: As much as I would like to try vanilla kernel, I don't want to break my system. I use Debian Stable, don't know if things would just work with vanilla kernel. You may try bookworm-backports kernel 6.6.13+bpo-amd64 You may check https://bugzilla.kernel.org/ for reports similar to your one.
Re: Regression in Radeon driver in latest Debian Stable kernel
On 15/05/2024 20:55, Michael Kjörling wrote: You made this bug report less than 48 hours ago. While I can certainly understand that you would like to see it fixed, that's not an inordinate amount of time to wait. What probably _would_ be helpful is to see whether you can recreate the same scenario with the vanilla kernel.org kernels of the same versions; confirming that the issue exists with the vanilla 6.1.90 kernel _and_ that the issue goes away when booting the vanilla kernel of whatever exact version your earlier package is (I'm guessing 6.1.85), both when built with the same configuration options as the kernels shipped by Debian. That would confirm whether what you are seeing is something somehow introduced by Debian, or an upstream bug. Thank you for your reply, I appreciate it. I found out that this error happened on previous version of the kernel as well, just found it in the logs. So, it's not an immediate regression in the latest version of the kernel in Debian. Maybe it's deeper than that. That lowers the possibility that this is the most recent update which brought this problem. I sent latest update to the bug report, I will wait for any reply from developer but no rush, of course. As much as I would like to try vanilla kernel, I don't want to break my system. I use Debian Stable, don't know if things would just work with vanilla kernel. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: DNI electrónico en Debian
Estoy usando el típico Sveon que se muestra en la lista. Yo también lo uso como método de autenticación al sistema mediante pam_pkcs11. El Fri, 3 May 2024 19:56:51 +0200 Camaleón va escriure el següent: > El 2024-05-03 a las 09:57 -0600, Alejandro G. Sanchez Martinez > escribió: > > > En 02/05/24 01:41, Listas escribió: > > > El jue, 02-05-2024 a las 09:10 +0200, Camaleón escribió: > > > > > > > > Quienes usáis un lector autónomo y os funciona bien, mejor si > > > > decís marca, modelo (chipset) y tipo de conexión, seguro que > > > > resulta de utilidad para quien pregunta y para futuros lectores > > > > de este hilo :-) > > > En concreto en mi caso es > > > > > > lector USB Alcor Micro AU9540. > > > > > > Pero cualquier lector que cumpla con la especificación CCID > > > debería valer, básicamente todos los que se venden a día de hoy. > > > > > > Una lista de equipos soportados: > > > https://ccid.apdu.fr/ccid/section.html > > > > > > Info de opensc: > > > https://github.com/OpenSC/OpenSC/wiki/Smart-card-readers-%28Linux-and-Mac-OS-X%29 > > > > > > La especificación CCID: > > > https://www.usb.org/sites/default/files/DWG_Smart-Card_CCID_Rev110.pdf > > > > > > Un saludo > > > > > > > > Para lso que estasmo fuera de España si nos pudieran dar > > informaci+on de para que lo utilizan o cuales serían su > > funcuionalidad se lo agradeceriamos > > En España concretamente¹ es equivalente a la firma manuscrita, con lo > que ello conlleva a efectos legales, jurídicos, administrativos y de > todo tipo. > > Tanto el DNI electrónico (en soporte material de tarjeta física que > integra un certificado digital) como el certificado electrónico > cualificado (certificado en soporte software, es un archivo > informático) se usan para identificarte/acreditarte ante cualquier > instancia o entidad público y/o privada (gobierno, administraciones > locales, empresas, contratos privados, etc...). > > Realmente útil tanto para personas físicas como para personas > jurídicas (empresas o sus representantes). > > ¹Su uso es bastante desigual en otros países de la UE/EEE/Suiza, > siendo Reino Unido caso aparte donde apenas se usa, al menos según mi > experiencia personal. > > Saludos, >
Re: Regression in Radeon driver in latest Debian Stable kernel
On 15 May 2024 20:40 +0100, from pior...@gmx.com (piorunz): > I have reported a regression in latest Linux kernel in Debian Stable: > > segfault at amdgpu_dm_atomic_commit_tail > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071080 You made this bug report less than 48 hours ago. While I can certainly understand that you would like to see it fixed, that's not an inordinate amount of time to wait. What probably _would_ be helpful is to see whether you can recreate the same scenario with the vanilla kernel.org kernels of the same versions; confirming that the issue exists with the vanilla 6.1.90 kernel _and_ that the issue goes away when booting the vanilla kernel of whatever exact version your earlier package is (I'm guessing 6.1.85), both when built with the same configuration options as the kernels shipped by Debian. That would confirm whether what you are seeing is something somehow introduced by Debian, or an upstream bug. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
Regression in Radeon driver in latest Debian Stable kernel
Hello, I have reported a regression in latest Linux kernel in Debian Stable: segfault at amdgpu_dm_atomic_commit_tail https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071080 It throws a lot of errors related to AMD GPU every day. I also experienced full desktop hang, where I had to restart my computer: https://bugs.kde.org/show_bug.cgi?id=486970 This happens on 6.1.0-21-amd64. Booting previous version 6.1.0-20-amd64 solves all problems. Can anyone help me with getting attention from some developers? KDE dev said this is downstream, not KDE problem. Debian bug reported, but no reply from anyone yet. -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Serial Connection in Debian 9 Moxa Device
Hello Debian Team, We are using Linux Debain 9 in our moxa devices. we are connected in a network where we connect with our moxa device via ssh and run the commands with Gauge ip and port and get Data. Now I'm Facing issue from 2, 3 weeks to connect the moxa using ssh and then connect to the serial port and get data as i getting in Telnet. I need Your Help in this Scenario to get the data when i connect through serial cable. please Let me know ASAP. Thanks Faisal
Re: Probléme de clés et dépôts Debian
Le dimanche 12 mai 2024 à 15:23 +0200, didier gaumet a écrit : > > donc en gros je pense que tu n'as rien à faire, qu'avec le temps, les > paquets Debian le nécessitant seront modifiés et que les dépôts le > nécessitant seront signés par des clés plus robustes (algo' plus > fiable) > > Bon, je vais patienter un peu, car pour l'heure ça me donne un accès aux dépôts. Nous verrons par la suite. Merci de vos réponses en tous cas. Krystof26
Re: Probléme de clés et dépôts Debian
Bonjour, - ce sont seulement des avertissements (W) pas des erreurs (E) - tu es dans un mélange stable et testing - par définition testing c'est fait pour tester donc tu te retrouves avec des trucs pas encore bien finalisés (on peut utiliser testing, unstable et experimental, faut juste accepter qu'on doit pouvoir se débrouiller seul: Debian ne met pas ça à disposition pour utiliser mais pour tester dans le but que Debian stable soit... stable) mon impression (je peux me tromper...) est que tout ça provient d'un travail de sécurisation en cours pour s'assurer que les dépôts lors des mises-à-jour sont bien ceux qu'ils prétendent être. Cela semble nécessiter qu'ils soient signés par des algorithmes sûrs, et que apt comme gpg permettent de s'assurer que l'algorithme utilisé est sûr. Et là on dirait que apt a déjà été modifié pour verifier ça mais que gpg ne sait pas quoi en faire (soit gpg devra être modifié soit il sait déjà traiter ça mais il reçoit des options erronées de apt qui devra être modifié (peut-être seulement les valeurs par défaut)) Ubuntu a un petit topo là-dessus et il est probable que c'est la même chose ici (particulièrement en bas de page, les trucs sur l'algo' dans apt.conf): https://discourse.ubuntu.com/t/new-requirements-for-apt-repository-signing-in-24-04/42854 donc en gros je pense que tu n'as rien à faire, qu'avec le temps, les paquets Debian le nécessitant seront modifiés et que les dépôts le nécessitant seront signés par des clés plus robustes (algo' plus fiable)
Re: Probléme de clés et dépôts Debian
Bonjour, As-tu essayé de nettoyer la bibliothèque et les caches APT ? Cel force APT à reconstituer sa base. # \rm -Rf /var/lib/apt* /var/cache/apt* Recréer la racine « aptitude : # mkdir /var/lib/aptitude et relancer une mise à jour : # aptitude update > Le 12 mai 2024 à 12:52, Christophe Musseau a écrit : > > Bonjour la liste, > > Ces derniers temps pas mal de mise à jour, et notamment avec Testing. > Consécutivement à une de ces récentes mise à jour, quand je lance # > aptitude update, j'ai droit aux messages suivants. Cela ne m'empêche > pas d'effectuer les mises à jour, mais je ne comprends pas et n'arrive > pas à résoudre ce problème avec les clés. > > Messages : > W: > http://debug.mirrors.debian.org/debian-debug/dists/testing-debug/InRelease > : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: > http://security.debian.org/debian-security/dists/bookworm-security/InRelease > : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: > Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: http://deb.debian.org/debian/dists/bookworm/InRelease: Unknown > response from gpgv to --assert-pubkey-algo check: gpgv: error: Error > parsing command-line arguments > W: http://deb.debian.org/debian/dists/bookworm-updates/InRelease: > Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: http://deb.debian.org/debian/dists/testing/InRelease: Unknown > response from gpgv to --assert-pubkey-algo check: gpgv: error: Error > parsing command-line arguments > W: > http://deb.debian.org/debian-security/dists/testing-security/updates/InRelease > : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > W: http://deb.debian.org/debian/dists/testing-updates/InRelease: > Unknown response from gpgv to --assert-pubkey-algo check: gpgv: > error: Error parsing command-line arguments > > Si quelqu'un a une solution à me proposer. > Merci par avance > > Krystof26 > -- Pierre Malard Responsable architectures système CDS DINAMIS/THEIA Montpellier IRD - UMR Espace-Dev - UAR CPST - IR Data-Terra Maison de la Télédétection 500 rue Jean-François Breton 34093 Montpellier Cx 5 France Tél : +33 626 89 22 68 «Il vaut mieux passer à La Poste qu’à la postérité» Alphonse Allais |\ _,,,---,,_ /,`.-'`'-. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <-- signature.asc Description: Message signed with OpenPGP
Probléme de clés et dépôts Debian
Bonjour la liste, Ces derniers temps pas mal de mise à jour, et notamment avec Testing. Consécutivement à une de ces récentes mise à jour, quand je lance # aptitude update, j'ai droit aux messages suivants. Cela ne m'empêche pas d'effectuer les mises à jour, mais je ne comprends pas et n'arrive pas à résoudre ce problème avec les clés. Messages : W: http://debug.mirrors.debian.org/debian-debug/dists/testing-debug/InRelease : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://security.debian.org/debian-security/dists/bookworm-security/InRelease : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: https://dl.google.com/linux/chrome/deb/dists/stable/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian/dists/bookworm/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian/dists/bookworm-updates/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian/dists/testing/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian-security/dists/testing-security/updates/InRelease : Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments W: http://deb.debian.org/debian/dists/testing-updates/InRelease: Unknown response from gpgv to --assert-pubkey-algo check: gpgv: error: Error parsing command-line arguments Si quelqu'un a une solution à me proposer. Merci par avance Krystof26
Re: How to create a custom Debian ISO
Hi, Aditya Garg wrote to debian-devel: > > I wanted to create a custom ISO of Debian, with the following > > customisations: > > 1. I want to add a custom kernel that supports my Hardware. > > 2. I want to add my own Apt repo which hosts various software packages to support my hardware. > > I am not able to get any good documentation for the same. Please help. Marvin Renich wrote: > The package live-build from the Debian Live project might help you do > what you want. Indeed the live-build package seems to be in use outside Debian's own ISO production. Mailing list is debian-l...@lists.debian.org There exists a manual https://live-team.pages.debian.net/live-manual/html/live-manual/index.en.html Installation ISOs are made by package debian-cd, of which i am not aware that it would have have users outside the official ISO production.i Mailing list is debian...@lists.debian.org Your impression about lack of documentation is not wrong as far as this project is concerned. :)) Nevertheless the production step of packing up the ISO from a prepared file tree is documented together with methods to use a Debian installation ISO as base for the preparation: https://wiki.debian.org/RepackBootableISO Packages may probably be added at the appropriate place in the directory tree under /pool. (Managing a Debian repo is not my turf. Sorry for being vague here.) Changing the content of a Debian ISO might need some follow-up work in administrative files of the ISO. When merging Debian ISOs, my script https://dev.lovelyhq.com/libburnia/libisoburn/raw/branch/master/test/merge_debian_isos manipulates: /README.txt /dists/*/Release and merges the files listed in /dists/*/Release. You would have to explore whether these files are affected by your changes. Have a nice day :) Thomas
Re: How to create a custom Debian ISO
* Aditya Garg [240511 05:15]: > Hello > > I wanted to create a custom ISO of Debian, with the following customisations: > > 1. I want to add a custom kernel that supports my Hardware. > 2. I want to add my own Apt repo which hosts various software packages to > support my hardware. > > I am not able to get any good documentation for the same. Please help. [Redirecting to debian-user, dropping -project, M-F-T set to debian-user only] First, please don't double-post the same message within a few minutes. Give your message at least a half hour to show up before you decide it wasn't received. Second, neither debian-devel nor debian-project are appropriate lists for this question. You should use debian-user@lists.debian.org or some other user-oriented forum. Also, posting a question to multiple lists at once (called cross-posting) is considered rude in most situations. To give a possible answer to your question, look at the Debian Live project: https://www.debian.org/devel/debian-live/ The package live-build from the Debian Live project might help you do what you want. ...Marvin
Re: debian bookworm japanese kana input disabled
Hi Updated and upgraded,autoremoved. This matter has been fixed. The problem is currently resolved. Nice follow up! I appreciate it. Best wishes -- Moliharu Tomizawa
Re: Debian no es tan fácil como dicen
On Fri, May 10, 2024 at 11:45:25AM -0400, Carlos Garcia Elmis wrote: > Hola equipo Debian, soy nuevo en Linux/GNU y en si no es una correo de > queja si no de ampliar Debian, no solo instale Debian si no también un > montón de sus derivados, y en todos menos en una fue que me facilito la > vida y estoy hablando de deepin: > ¿cuales son las ventajas de deepin sobre Debian? > R: en deepin pude desinstalar programas desde su menu inicio, también pude > restaurar el sistema por último y que es lo primero que se hace es que la > instalación del SO de deepin es súper Fasil, mucho mas que calamares > Disculpe: debo decirte que se suele hablar ingles in esta lista. Puede ser que debian-user-spanish seria mejor. Como dice el FAQ mensual - Otras distribuciones de Linux son "off-topic" por aqui asi tu mensaje no valga mucho. Apologies: I have to tell you that we normally speak English in this list It might be that debian-user-spanish would be better. As it says in the monthly FAQ: Other Linux distributions are off topic here: your message is not worth as much here. Saludos / with every good wish, Andy Cater [amaca...@debian.org] > Pero en este caso vengo a hablarles de los dos primeros puntos de deepin > sobre Debian > 1) Un usuario nuevo como yo al pasarse a Debian necesita probar nuevas > aplicaciones para dejar atrás las que ya uso, en deepin instalaba y > desinstala las app sin problema, en Debian no, LibreOffice (sudo apt > remover install), GIMP (sudo apt remover GIMP), etc, en deepin clic en menú > inicio, clic derecho sobre la app y desinstalar, yo me pregunto cómo > quieren que alguien nuevo se quede en Debian si al mismo tiempo que tenemos > que probar aplicaciones por qué es un SO diferente no podemos desinstalar > aplicaciones tan fácil como la instalamos con gdebi > Nota:para esta parte solo incluye paquetes nativos ya que si hablamos de > flatpak, snapd y appimage es diferente sin embargo todos terminamos > evitando estas alternativa por que aumenta el consumo de las aplicaciones > además de ser contenedores y no ajustarse a la configuración del sistema > por tal motivo > > 2)Deepin tiene la posibilidad de restaurar el sistema dando una clara > ventaja de que un nuevo usuario que hizo y deshizo en deepin las veces que > quiso le da la oportunidad de volver a configurar de nuevo una nueva > cuenta, colocar el idioma, sin estar particionado otra vez el disco o > reinstalando el sistema desde cero, la gran desventaja de deepin aquí es > que si hago una partición manual pierdo esta excelente configuración de > deepin, por tal motivo estuve un buen tiempo en deepin > > Sin embargo no todo es bello en deepin, siendo que ellos no tienen una > interfaz única y bella gracias a deepin deskop, no por eso la instale y me > quedé bastante tiempo con ella si no por esa tres características que > mencioné atrás, pero vamos a la desventaja en deepin > > Como ya sabemos ya hablamos de los contenedores que habitualmente todos > evitamos por el uso mayor de recursos a comparación de un app nativo, pero > no siempre podemos evitarlos sobre todo con app que no podemos encontrar > nativas para Debian por tal motivo he aquí la única ventaja y por su puesto > gran ventaja de Debian sobre deepin, ya se dije que no era buena idea pero > también es inevitable sus usos, y claro hablo de flatpak, snap y appimage > que si bien cualquiera podemos utilizar en deepin pero perdiendo la > facilidad de uso desde la tienda como Debian nos proporciona estos paquetes > > Otro punto es que los repositorios Debian están disponibles para todo el > mundo y son veloces en cambio deepin no tienen esa gran ventaja > > Resumiendo > 1) desinstalar software > 2)restablecer sistema > 3)instalar sistema > > Son puntos que para todo usuario nuevo es importante, deepin ha demostrado > que es posible tener un SO completo y es muy importante saber que deepin > busca independizarse de Debian así creando un deepin independiente > > Espero no haber molestado un saludo cordial a el gran equipo Debian, > bendiciones
Re: Debian no es tan fácil como dicen
On Fri, May 10, 2024 at 11:45:25AM -0400, Carlos Garcia Elmis wrote: > Hola equipo Debian, soy nuevo en Linux/GNU y en si no es una correo de > queja si no de ampliar Debian, no solo instale Debian si no también un > montón de sus derivados, y en todos menos en una fue que me facilito la > vida y estoy hablando de deepin: [...] ¡Hola, Carlos! - No hay equipo aquí: esta es la lista de los usuarios - Si quieres hablar con usuarios en castellano, por aquí hay una lista en este lenguaje: https://en.wikipedia.org/wiki/Variant_Call_Format Quizás sea más apropiada para ti (la mayoría de la gente aquí no entiende castellano) - Me alegro mucho que te guste Deepin; sin embargo, aquì encontrarás gente que usa Debian y lo prefiere así (yo soy uno de esos). Tengo dudas de que una misiva como la tuya sea ùtil en este caso. Saludos -- tomás signature.asc Description: PGP signature
Debian no es tan fácil como dicen
Hola equipo Debian, soy nuevo en Linux/GNU y en si no es una correo de queja si no de ampliar Debian, no solo instale Debian si no también un montón de sus derivados, y en todos menos en una fue que me facilito la vida y estoy hablando de deepin: ¿cuales son las ventajas de deepin sobre Debian? R: en deepin pude desinstalar programas desde su menu inicio, también pude restaurar el sistema por último y que es lo primero que se hace es que la instalación del SO de deepin es súper Fasil, mucho mas que calamares Pero en este caso vengo a hablarles de los dos primeros puntos de deepin sobre Debian 1) Un usuario nuevo como yo al pasarse a Debian necesita probar nuevas aplicaciones para dejar atrás las que ya uso, en deepin instalaba y desinstala las app sin problema, en Debian no, LibreOffice (sudo apt remover install), GIMP (sudo apt remover GIMP), etc, en deepin clic en menú inicio, clic derecho sobre la app y desinstalar, yo me pregunto cómo quieren que alguien nuevo se quede en Debian si al mismo tiempo que tenemos que probar aplicaciones por qué es un SO diferente no podemos desinstalar aplicaciones tan fácil como la instalamos con gdebi Nota:para esta parte solo incluye paquetes nativos ya que si hablamos de flatpak, snapd y appimage es diferente sin embargo todos terminamos evitando estas alternativa por que aumenta el consumo de las aplicaciones además de ser contenedores y no ajustarse a la configuración del sistema por tal motivo 2)Deepin tiene la posibilidad de restaurar el sistema dando una clara ventaja de que un nuevo usuario que hizo y deshizo en deepin las veces que quiso le da la oportunidad de volver a configurar de nuevo una nueva cuenta, colocar el idioma, sin estar particionado otra vez el disco o reinstalando el sistema desde cero, la gran desventaja de deepin aquí es que si hago una partición manual pierdo esta excelente configuración de deepin, por tal motivo estuve un buen tiempo en deepin Sin embargo no todo es bello en deepin, siendo que ellos no tienen una interfaz única y bella gracias a deepin deskop, no por eso la instale y me quedé bastante tiempo con ella si no por esa tres características que mencioné atrás, pero vamos a la desventaja en deepin Como ya sabemos ya hablamos de los contenedores que habitualmente todos evitamos por el uso mayor de recursos a comparación de un app nativo, pero no siempre podemos evitarlos sobre todo con app que no podemos encontrar nativas para Debian por tal motivo he aquí la única ventaja y por su puesto gran ventaja de Debian sobre deepin, ya se dije que no era buena idea pero también es inevitable sus usos, y claro hablo de flatpak, snap y appimage que si bien cualquiera podemos utilizar en deepin pero perdiendo la facilidad de uso desde la tienda como Debian nos proporciona estos paquetes Otro punto es que los repositorios Debian están disponibles para todo el mundo y son veloces en cambio deepin no tienen esa gran ventaja Resumiendo 1) desinstalar software 2)restablecer sistema 3)instalar sistema Son puntos que para todo usuario nuevo es importante, deepin ha demostrado que es posible tener un SO completo y es muy importante saber que deepin busca independizarse de Debian así creando un deepin independiente Espero no haber molestado un saludo cordial a el gran equipo Debian, bendiciones
Re: Adding package to Debian Distro
On Thu 09 May 2024 at 16:24:55 (-), Curt wrote:
> On 2024-05-09, Charles Curley wrote:
> > On Thu, 9 May 2024 14:09:52 - (UTC) Curt wrote:
> >
> >> I don't think there is a process by which you could add closed-source
> >> IBM software to a bona fide Debian depository, even the non-free one,
> >> which only seems to contain firmware and drivers for closed-sourced
> >> *hardware*.
> >
> > Isn't that what the non-free archive is for?
> > https://www.debian.org/doc/debian-policy/ch-archive#s-non-free
>
> Maybe you're right. I can't seem to find a comprehensive list of
> non-free packages,
Would APT's lists do, assuming you have non-free in your sources.list?
/var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_non-free_{binary-amd64_Packages,i18n_Translation-en}
(Adjust for source address, distribution, architecture, language, etc.)
> nor anything equivalent to this intricate IBM
> software.
No idea. Cluster Technology is beyond my pay-grade.
> I mean, if non-free means: "anything at all that can be
> reverse-engineered by our software teams," then I've misunderstood its
> meaning and purpose (which is perfectly possible).
Well, no; you could have software that's gratis, open-source,
and redistributable, but if it couldn't be used, say, for
commercial purposes, that would have to go into Debian's
non-free archive rather than the main distribution.
It has nothing to do with reverse engineering per se.
Cheers,
David.
Re: Adding package to Debian Distro
On 2024-05-09, Charles Curley wrote: > On Thu, 9 May 2024 14:09:52 - (UTC) > Curt wrote: > >> I don't think there is a process by which you could add closed-source >> IBM software to a bona fide Debian depository, even the non-free one, >> which only seems to contain firmware and drivers for closed-sourced >> *hardware*. > > Isn't that what the non-free archive is for? > https://www.debian.org/doc/debian-policy/ch-archive#s-non-free > Maybe you're right. I can't seem to find a comprehensive list of non-free packages, nor anything equivalent to this intricate IBM software. I mean, if non-free means: "anything at all that can be reverse-engineered by our software teams," then I've misunderstood its meaning and purpose (which is perfectly possible).
Re: Adding package to Debian Distro
On Thu, 9 May 2024 14:09:52 - (UTC) Curt wrote: > I don't think there is a process by which you could add closed-source > IBM software to a bona fide Debian depository, even the non-free one, > which only seems to contain firmware and drivers for closed-sourced > *hardware*. Isn't that what the non-free archive is for? https://www.debian.org/doc/debian-policy/ch-archive#s-non-free -- Does anybody read signatures any more? https://charlescurley.com https://charlescurley.com/blog/
Re: Adding package to Debian Distro
On 2024-05-09, kiruthikaanbusuresh wrote: > > Hi Debian Team, > There is a package by name rsct which is specific to IBM. I would like to > know the process to get this added to the Debian Distro. Should I have > to get sponsorship for getting it added to Debian ? Seems IBM only provides a Ubuntu package. https://www.ibm.com/docs/en/rsct/3.2?topic=installation-verifying-linux-nodes Whether that package would work on your current Debian installation is anybody's guess (I am completely ignorant in these matters). I don't think there is a process by which you could add closed-source IBM software to a bona fide Debian depository, even the non-free one, which only seems to contain firmware and drivers for closed-sourced *hardware*. I could be wrong, though.
Re: Adding package to Debian Distro
On Thu, May 09, 2024 at 06:12:35PM +0530, kiruthikaanbusuresh wrote: > Hi Debian Team, > There is a package by name rsct which is specific to IBM. I would like to > know the process to get this added to the Debian Distro. Start with sharing more information about it. * Tell what "rsct" does (to get more stakeholders) * Where to find the source > Should I have to get sponsorship for getting it added to Debian ? You haven't told what the author[1] of rsct feels about that wish. > Thanks and Regards, > Kiruthika. NV Groeten Geert Stappers Footnote [1]: Copyrightholder -- Silence is hard to parse
Re: Adding package to Debian Distro
Hi, kiruthikaanbusuresh wrote: > Hi Debian Team, Standard disclaimer: We are the users. A team only by coincidence. (And you seem not to be subscribed to the mailing list. Thus i CC: your mail address.) > There is a package by name rsct which is specific to IBM. I > would like to know the process to get this added to the Debian Distro. If it complies to https://wiki.debian.org/DebianFreeSoftwareGuidelines and is of some general use, then have a look at https://wiki.debian.org/RFP > Should I have to get sponsorship for getting it added to Debian ? If you want to contribute own work to this packaging endeavor: Yes. It will probably increase your chances for success. See https://mentors.debian.net/ https://wiki.debian.org/ITP Have a nice day :) Thomas
Re: debian bookworm japanese kana input disabled
On Donnerstag, 9. Mai 2024 08:48:03 -04 Brad Rogers wrote: > On Thu, 9 May 2024 10:06:29 + > Michael Kjörling <2695bd53d...@ewoof.net> wrote: > > Hello Michael, > > >However, I seem to have had a similar issue even after upgrading to > >the first regression-fixed glib2.0 packages on Bookworm. > >Specifically, dead keys no longer working with the Swedish keyboard > >layout, and instead acting as though I didn't press any key at all. > > Is it possible that, without at least logging out and back in, the > broken version of the library is still in use? Hi Michael and hello 冨澤守治[1] I don't know if it was related but with the same Debian Sid upgrade Firefox (and only Firefox) lost the ability to enter äöüáéí€ß ... that is it ignored anything which was not pure ASCII, however entering the accented characters in a terminal or other applications (here KDE) still worked. After today's upgrade everything was back to normal but I *had* to reboot. So logging out and back in again might work although I suspect that at least restarting the X server will be necessary. I didn't try it because I had to reboot anyway. All the best to you all -- Eike Lantzsch KY4PZ / ZP5CGE [1] mailto: %3D%3Futf-8%3FB%3F5Yao5r6k5a6I5rK7%3F%3D%20%3Cmolitz%40coffee.ocn.ne.jp%3E
Adding package to Debian Distro
Hi Debian Team, There is a package by name rsct which is specific to IBM. I would like to know the process to get this added to the Debian Distro. Should I have to get sponsorship for getting it added to Debian ? Thanks and Regards, Kiruthika. NV
Re: debian bookworm japanese kana input disabled
On Thu, 9 May 2024 10:06:29 +
Michael Kjörling <2695bd53d...@ewoof.net> wrote:
Hello Michael,
>However, I seem to have had a similar issue even after upgrading to
>the first regression-fixed glib2.0 packages on Bookworm. Specifically,
>dead keys no longer working with the Swedish keyboard layout, and
>instead acting as though I didn't press any key at all.
Is it possible that, without at least logging out and back in, the
broken version of the library is still in use?
--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
Words as weapons, sharper than knives
Devil Inside - INXS
pgpLB3jEQkwp1.pgp
Description: OpenPGP digital signature
Re: DNI electrónico en Debian
No tuve que tocar ni configurar nada, que yo recuerde. Un saludo. El jue, 9 may 2024, 12:36, Borja Gutiérrez Fernández escribió: > Hola, > > Perdón por el cambio de tema, actualizaste de 11 a 12 sin ningún problema? > > > Gracias. > Borja Gutiérrez Fernández. > El 1/5/24 a las 20:22, Raúl Armenta escribió: > > Yo lo hago. Instalé en Debian 11 y se mantiene todo correcto después de > que actualicé al 12. > > Configurado sobre Firefox. > > Único inconveniente que no he sabido configurar, firmar externamente con > aplicaciones de cada organismo. No encuentra el almacén de certificados de > Firefox. Tengo que guardar mi certificado en disco. > > También utilizo con lector de DNI electrónico. > > Un saludete > > El mié, 1 may 2024, 20:16, Luis Muñoz Fuente < > luis.munoz@juntadeandalucia.es> escribió: > >> Hola a todos/as: >> >> ¿Alguien se identifica o firma con el DNI electrónico en Debian? >> Habitualmente uso el certificado digital de la FNMT pero estoy pensando >> comprar un lector de DNI por si me falla la firma con el certificado de la >> FNMT. >> >> Saludos >> >
Re: DNI electrónico en Debian
Hola, Perdón por el cambio de tema, actualizaste de 11 a 12 sin ningún problema? Gracias. Borja Gutiérrez Fernández. El 1/5/24 a las 20:22, Raúl Armenta escribió: Yo lo hago. Instalé en Debian 11 y se mantiene todo correcto después de que actualicé al 12. Configurado sobre Firefox. Único inconveniente que no he sabido configurar, firmar externamente con aplicaciones de cada organismo. No encuentra el almacén de certificados de Firefox. Tengo que guardar mi certificado en disco. También utilizo con lector de DNI electrónico. Un saludete El mié, 1 may 2024, 20:16, Luis Muñoz Fuente escribió: Hola a todos/as: ¿Alguien se identifica o firma con el DNI electrónico en Debian? Habitualmente uso el certificado digital de la FNMT pero estoy pensando comprar un lector de DNI por si me falla la firma con el certificado de la FNMT. Saludos
Re: debian bookworm japanese kana input disabled
On 9 May 2024 09:14 +0200, from f.rou...@free.fr (Florent Rougon): >> Last night (JST) I did some apt update && apt upgade. >> But all of sudden I can't input kana and even print any editer or calc cell. >> (Roman alphabet has no problem on printing.) > > This may be due to a recent glib2.0 update: > > https://lists.debian.org/debian-security-announce/2024/msg00094.html That was my thought as well. > “The update for glib2.0 released as DSA 5682-1 caused a regression in > ibus affecting text entry with non-trivial input methods. Updated > glib2.0 packages are available to correct this issue.” > > Hopefully, you just need to update again. However, I seem to have had a similar issue even after upgrading to the first regression-fixed glib2.0 packages on Bookworm. Specifically, dead keys no longer working with the Swedish keyboard layout, and instead acting as though I didn't press any key at all. The key press did show up in xev: KeyPress event, serial 33, synthetic NO, window 0x2a1, root 0x6aa, subw 0x0, time 1153798, (397,298), root:(1268,818), state 0x10, keycode 35 (keysym 0xfe57, dead_diaeresis), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 33, synthetic NO, window 0x2a1, root 0x6aa, subw 0x0, time 1153862, (397,298), root:(1268,818), state 0x10, keycode 35 (keysym 0xfe57, dead_diaeresis), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False but despite my attempts nothing showed up in any input field; trying with both Xfce's Mousepad text editor, KeepassXC and gnome-terminal to cover various UI toolkits, with the same result everywhere. The combination of the key press showing up in xev and nothing showing up in any application I tried with running under X pointed strongly toward the input translation layer. However, another physical computer also running Bookworm which I upgraded to latest at around 09:40 May 9 UTC _didn't_ seem to have the same issue, despite being set up similarly. Turned out that there is _another_ upgrade to libglib2.0-0 and friends taking those packages to package version 2.74.6-2+deb12u2; after installing _that_ upgrade and rebooting, dead keys again seem to work normally. (It's entirely possible that the reboot wasn't needed, but as I had only just rebooted the system and so didn't have much of anything already open, it seemed an easy enough way to actually ensure that everything was running at the newly upgraded version.) So if you're still having the same issue, _try once more_ apt-get update && apt-get -u dist-upgrade; double-check that you get the +deb12u2 or newer glib package versions; and see if that fixes the problem before you poke around too much with the configuration (and risk breaking something else in the process). Then let us know whether you're still having the same issue or whether that resolved it. -- Michael Kjörling https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
