March 2023 - openSUSE Users - openSUSE Mailing Lists

[oS-en] about epson1:libusb: scanner
by Carlos E. R. 11 Apr '23

11 Apr '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I had a bug that have been nagging me for a few years, for forgetting to report. I plugged my Epson scanner (Perfection 1650): <0.6> 2023-03-27T13:42:49.583719+02:00 Telcontar kernel - - - [145303.237970][T12173] usb 3-1: new full-speed USB device number 3 using xhci_hcd <0.6> 2023-03-27T13:42:49.919401+02:00 Telcontar kernel - - - [145303.574601][T12173] usb 3-1: New USB device found, idVendor=04b8, idProduct=0110, bcdDevice= 3.02 <0.6> 2023-03-27T13:42:49.919413+02:00 Telcontar kernel - - - [145303.574606][T12173] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 <0.6> 2023-03-27T13:42:49.919414+02:00 Telcontar kernel - - - [145303.574608][T12173] usb 3-1: Product: EPSON Scanner <0.6> 2023-03-27T13:42:49.919415+02:00 Telcontar kernel - - - [145303.574609][T12173] usb 3-1: Manufacturer: EPSON I opened up gimp, selected File, Create Xsane device dialog. Then I would select the first entry in the photo, using epson2 library: https://paste.opensuse.org/pastes/d884de97a177 An one day, suddenly, that library failed, and I had to select the "epson" library instead. That could be Leap 15.2 or 15.3. So, today, as I was going to scan some papers I remembered and decided to report, so started to take notes as I prepared the scanner. And today it works! Heisenbug? :-o - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZCGEhhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVyHMAniPFPeEFYWOu21cytI55 Ge1W/16/AJ0bLkQWAyx5nE70wnYIu7Rnx2mCKw== =KKdI -----END PGP SIGNATURE-----

3 7

[oS-en] Instant message client?
by Carlos E. R. 03 Apr '23

03 Apr '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Do we have some instant message client? Something that can send a text message to a mobile phone, from a script? Say whatsapp, signal, telegram... :-? - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZCFgzhwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVsjEAn3Ssx4aen17N/zV55ccI AZ8IwlKOAJ4403ez85yFtAbNu2cGXAAeA6yjPQ== =TouZ -----END PGP SIGNATURE-----

16 54

Re: four or maybe six modules
by Per Jessen 01 Apr '23

01 Apr '23

gebser(a)mousecar.com wrote: > It's been a very long time since I messed with modules. And I never > enjoyed running insmod or modprobe and then-- probably-- having to run > rmmod... and that was back when there were four or maybe six modules > to deal with. Now we have > > # lsmod|wc -l > 177 Here only 71 with the latest TW (i586). Only 59 on a Raspi. On the openSUSE mailing list server, only 40. There are also times when modules are loaded unnecessarily. I think even the 2.2 series kernel had more than four or five modules :-) Much will depend on what you do with your Linux systems, how many you have and how varied they are. How much you dabble with the hardware. -- Per Jessen, Zürich (15.7°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

4 10

Re: Heads up: removing the mkinitrd wrapper
by Per Jessen 01 Apr '23

01 Apr '23

Carlos E. R. wrote: > On 2023-03-30 18:42, Per Jessen wrote: >> Carlos E. R. wrote: >> >>> Or, copy the old script to /usr/local/sbin, unless that is not >>> advisable. >> >> Or - oh horror - move with the times. > > I think I'm entitled to be recognized as an old fart by now :-p I'm sure you are, but does that prevent you from moving with the times? >> I still think the main point is that you don't actually dabble with >> building initrds yourself, you are happy to follow instructions to do >> so, when needed. In the future, no one is going to direct you to run >> mkinitrd, so what is the point of having an alias. > > Per, > > You may have read from me and Andrei the multiples scenarios in which > people have to run mkinitrd manually. I have been in most of them. No, I have totally missed that. I thought you were talking about having to create initrds manually. For the last couple of years, I have not been in a single situation where I _had_ to run mkinitrd. dracut was very useful though. -- Per Jessen, Zürich (16.2°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

7 11

Re: [oS-EN] Question on full disk encription
by David C. Rankin 01 Apr '23

01 Apr '23

On 3/28/23 08:01, cagsm wrote: > On Tue, Mar 28, 2023 at 12:42 PM Carlos E. R. > <robin.listas(a)telefonica.net> wrote: >> new laptop here, and I decided to install Leap 15.4 with full disk >> encryption, no LVM (a feature I wanted to have for years, so I'm happy). >> It asks for the password twice (contrary to my customs, I'm using plymouth). >> It asks once before grub loads. Well, ok, there is no separate /boot, so >> it has to read "/" which is encrypted. Nice. >> But after selecting the boot entry in grub, it asks again. Once, despite >> being 3 partitions ("/", "/boot" and swap). Ok. > > doesnt the official opensuse pages state about the situation about > double entry of passphrases. i have double passphrase questionaire as > well with 15.4 fresh install via the propsed partition setup on a > notebook. btrfs or something and the snapshot filesystem stuff and > all. not expert though > >> <https://en.opensuse.org/SDB:Encrypted_root_file_system#Avoiding_to_type_the…> The page says: <quote> Warning: Do this only if you have an encrypted root partition **that includes /boot** (no separate /boot partition)! The key added to the initrd can be used to decrypt your root partition, therefore having the initrd on an unencrypted /boot partition would defeat encrypting your root partition. </quote> How do you handle the case of a separate /boot partition? -- David C. Rankin, J.D.,P.E.

4 10

leap 15.5 install - keyboard question
by Per Jessen 31 Mar '23

31 Mar '23

I'm just starting a test installation, and I used X mode by mistake - the machine had a former life and X was enabled by default (.ssh/config). In the YaST GUI (which looks really good, btw), I change locale to UK English, then keyboard to US English. It's just our normal setting, muscle memory. While YaST was doing whatever, I switched to a libreoffice document and realised the keyboard had changed. Presumably to US English. I'll wait and see if it switches back, but is this change to be expected? When we do a "normal" install without X, changing the keyboard layout only takes effect for the system being installed. -- Per Jessen, Zürich (14.9°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

3 10

[oS-EN] Machine for disk encryption password happens too fast.
by Carlos E. R. 31 Mar '23

31 Mar '23

Hi, New machine (Lenovo L14 Gen3). Full disk encryption using discrete partitions with the same password ("/", "/home", swap). On boot, the Lenovo logo flashes instantly and the prompt for the disk encryption key pops fast. At this point, ctr-alt-del is ignored. There is no time nor message to press F1 for bios config or F12 for boot menu. I have to press and hold the power button for 4 seconds to power off, then power up again, and start pressing F1 or F12 fast, so that it is read. Slow pressing doesn't work. Press F1 and hold doesn't work. Question: Is it possible to insert a delay? -- Cheers / Saludos, Carlos E. R. (from Telcontar, using openSUSE Leap 15.4)

4 12

With all the talk about WiFi lately
by joe a 30 Mar '23

30 Mar '23

Another FYI from Mr. Sunshine: https://www.theregister.com/2023/03/30/wifi_spec_ambiguity_leak/?td=rt-3a

1 0

Re: Heads up: removing the mkinitrd wrapper
by Per Jessen 30 Mar '23

30 Mar '23

Simon Becherer wrote: > Am 30.03.23 um 18:42 schrieb Per Jessen: >> Carlos E. R. wrote: >> >>> Or, copy the old script to /usr/local/sbin, unless that is not >>> advisable. >> >> Or - oh horror - move with the times. >> >> I still think the main point is that you don't actually dabble with >> building initrds yourself, you are happy to follow instructions to do >> so, when needed. In the future, no one is going to direct you to run >> mkinitrd, so what is the point of having an alias. >> >> > well, the instructions you will google will lack 1 or 2 years... Some of them will, no doubt. Others might just say "rebuild your initrd". If Carlos is at that point - googling, having to apply his own imagination, read a man page - he'll work it out. > and you will somtimes face a bug for the workaround you will > nee to do yourselfe a mkinitrd. example: > https://bugzilla.opensuse.org/show_bug.cgi?id=1181768 Certainly, that will always remain. I build my own initrds all the time. http://bugzilla.opensuse.org/show_bug.cgi?id=1206781 > but this mails here will move away from the original post/problem, > so maybe we should stop or go to another list. I very much agree. -- Per Jessen, Zürich (16.3°C) What is "querulant" in Englisch?

3 3

Fwd: 20230326 last snapshot to contain i586 in the main repo
by Andrei Borzenkov 30 Mar '23

30 Mar '23

---------- Forwarded message --------- From: Dominique Leuenberger <dimstar(a)opensuse.org> Date: Tue, Mar 28, 2023 at 2:00 PM Subject: 20230326 last snapshot to contain i586 in the main repo To: <factory(a)lists.opensuse.org> Another heads-up to the i586 users, Snpashot 20230326 is the last snapshot that will carry i586 binaries in the main repositories. If you are running a 32-bit installation of Tumbleweed, make sure to check your repositories and have them point to the correct locations: OSS: http://download.opensuse.org/ports/i586/tumbleweed/repo/oss/ NON-OSS: http://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss/ Update: http://download.opensuse.org/ports/i586/update/tumbleweed/ Starting with Snapshot 0328, the i586 binaries will no longer be shipped in the main repository. Cheers, Dominique

5 15