- openSUSE Users

tumbleweed: I have an unknown directory in home
by Stakanov 21 Dec '24

21 Dec '24

/home/osrt-repo-checker I have this directory in my home directory. I have no pale idea what program did create it in /home In the properties it does not belong to a user and a group. Does anybody has an idea what is the directory "osrt-repo-checker"? Is this maybe a clamav thing? I found not reference in the internet. There is an OSRTT project for "checking LED monitor latency" but that cannot possibly be the one. Suggestions on how to find out? Thank you.

5 6

nvidia setup puzzler
by Marc Chamberlin 21 Dec '24

21 Dec '24

Hello - I have a system running OpenSuSE 15.5 KDE X11 Plasma desktop, with 2 monitors connect to it. It also has 2 nVidia Quadro K420 video cards, each connected to one of my two monitors. (This computer was given to me, I did not configure the hardware) I have wracked my brains trying to get both System Settings and nvidia-settings to set up the two terminals as clones and I have finally found a solution that works, but I do NOT grok as to why it works. I want to understand so that in the future I can figure out how video configuration works. The following is the non-working version of xorg.conf that was generated by nvidia-settings (with most of the comments removed) - > # nvidia-settings: X configuration file generated by nvidia-settings > # nvidia-settings: version 470.256.02 > > # nvidia-xconfig: X configuration file generated by nvidia-xconfig > # nvidia-xconfig: version 470.256.02 > # Section "Extensions" > # Option "Composite" "Disable" > # Option "RANDR" "Disable" > # EndSection > # Section "Screen" > # Identifier "Screen1" > # Device "Device1" > # Monitor "Monitor1" > # DefaultDepth 24 > # Option "Stereo" "0" > # Option "metamodes" "1920x1080 +0+0 {AllowGSYNC=Off}" > # Option "SLI" "On" > # Option "MultiGPU" "Off" > # Option "BaseMosaic" "Off" > # SubSection "Display" > # Depth 24 > # EndSubSection > # EndSection > > Section "ServerLayout" > Identifier "Layout0" > Screen 0 "Screen0" 0 0 > Screen 1 "Screen1" Relative "Screen0" 0 0 > InputDevice "Keyboard0" "CoreKeyboard" > InputDevice "Mouse0" "CorePointer" > Option "Xinerama" "0" > EndSection > > Section "Files" > EndSection > > Section "InputDevice" > Identifier "Mouse0" > Driver "mouse" > Option "Protocol" "IMPS/2" > Option "Device" "/dev/input/mice" > Option "Emulate3Buttons" "yes" > Option "ZAxisMapping" "4 5" > EndSection > > Section "InputDevice" > Identifier "Keyboard0" > Driver "kbd" > EndSection > > Section "Monitor" > Identifier "Monitor0" > VendorName "Unknown" > ModelName "Westinghouse Digital Electronics LVM-42w2" > DisplaySize 930 520 > HorizSync 30.0 - 80.0 > VertRefresh 60.0 - 75.0 > Gamma 2.2 > Option "DPMS" "true" > EndSection > > Section "Monitor" > Identifier "Monitor1" > VendorName "SAM" > ModelName "SAMSUNG" > DisplaySize 700 390 > HorizSync 15.0 - 68.0 > VertRefresh 24.0 - 75.0 > Gamma 2.2 > Option "DPMS" "true" > EndSection > > Section "Device" > Identifier "Device0" > Driver "nvidia" > VendorName "NVIDIA Corporation" > BoardName "Quadro K420" > BusID "PCI:3:0:0" > EndSection > > Section "Device" > Identifier "Device1" > Driver "nvidia" > VendorName "NVIDIA Corporation" > BoardName "Quadro K420" > BusID "PCI:4:0:0" > EndSection > > Section "Screen" > Identifier "Screen0" > Device "Device0" > Monitor "Monitor0" > DefaultDepth 24 > Option "UseEdid" "True" > Option "AllowEmptyInitialConfiguration" "True" > Option "nvidiaXineramaInfo" "FALSE" > Option "Stereo" "0" > Option "nvidiaXineramaInfoOrder" "DFP-0" > Option "metamodes" "nvidia-auto-select +0+0" > Option "SLI" "Off" > Option "MultiGPU" "Off" > Option "BaseMosaic" "off" > SubSection "Display" > Depth 24 > EndSubSection > EndSection > > Section "Screen" > Identifier "Screen1" > Device "Device1" > Monitor "Monitor1" > DefaultDepth 24 > Option "Stereo" "0" > Option "metamodes" "1920x1080 +0+0 {AllowGSYNC=Off}" > Option "SLI" "Off" > Option "MultiGPU" "Off" > Option "BaseMosaic" "off" > SubSection "Display" > Depth 24 > EndSubSection > EndSection > This produces a strange desktop display, Monitor 0 shows me just the open applications, Konsole windows and the mouse cursor. The mouse cursor is confined to just this one monitor and cannot be moved into what is shown on Monitor 1. That means this is not simply an extended desktop of some kind. Monitor 1 shows me the kicker bar, the background image, and the desktop icons. So it is as if half of the desktop items are being shown on one monitor and half on the other. And the mouse cursor cannot reach any of the components shown on one of the monitors, for example the start menu applications launcher. So after a lot of trials, I finally hit upon a solution. And that is to comment out one line in the ServerLayout section so it becomes this - > Section "ServerLayout" > Identifier "Layout0" > Screen 0 "Screen0" 0 0 > # Screen 1 "Screen1" Relative "Screen0" 0 0 > InputDevice "Keyboard0" "CoreKeyboard" > InputDevice "Mouse0" "CorePointer" > Option "Xinerama" "0" > EndSection and that works! The two monitors are now clones, showing everything on the desktop as expected. But I am totally baffled as to why! Commenting out the Screen 1 definition seems to remove half of what was configured by nvidia-settings. And there is nothing in xorg.conf that says the two monitors should be in a clone mode, I did set the two monitors in clone mode in system-settings. I don't grok how that fits in with xorg configuration since system-settings doesn't seem to make any changes to xorg.conf. Is there 2 setup approaches to configuring monitors that are in conflict with each other? My brain hurts, thanks for any enlightenment offered, Marc.

2 3

Is there any where to look to see if TW updates include CVE fixes or are just build dep updates?
by David C. Rankin 20 Dec '24

20 Dec '24

All, devs, Is there any page suse/openSUSE keeps that can tell us if the updates (upgrades) listed for TW are for security issues? When I just checked for the available updates, they in large part are just different point releases of the same 200 packages I upgraded 3 days ago. It would be helpful to know if the listed updates are security fixes or just point releases for some build dependency that was updated. Is there anywhere to find that information out? I know there is a security list, and that had that type of info on a per package basis (in a bit obscured format), but is that information captured anywhere else that doesn't take subscribing to another list or searching backwards through a list-archive? If not -- that would be another helpful addition. -- David C. Rankin, J.D.,P.E.

6 7

Re: Is there any where to look to see if TW updates include CVE fixes or are just build dep updates?
by -pj 20 Dec '24

20 Dec '24

On 12-20-2024 03:00PM, Patrick Shanahan wrote: > * -pj via openSUSE Users <users(a)lists.opensuse.org> [12-20-24 15:57]: >> >> >> On 12-20-2024 03:22AM, Masaru Nomiya wrote: >>> Hello, >>> >>> In the Message; >>> >>> Subject : Is there any where to look to see if TW updates include CVE fixes or are just build dep updates? >>> Message-ID : <f0cdcd93-9b66-4bb8-bc30-663dce2f1eca(a)gmail.com> >>> Date & Time: Thu, 19 Dec 2024 22:46:55 -0600 >>> >>> [DCR] == "David C. Rankin" <drankinatty(a)gmail.com> has written: >>> >>> DCR> All, devs, >>> >>> DCR> Is there any page suse/openSUSE keeps that can tell us if the updates >>> DCR> (upgrades) listed for TW are for security issues? When I just >>> DCR> checked for the available updates, they in large part are just >>> DCR> different point releases of the same 200 packages I upgraded 3 >>> DCR> days ago. It would be helpful to know if the listed updates are >>> DCR> security fixes or just point releases for some build dependency >>> DCR> that was updated. >>> [...] >>> >>> How about Change txt on >>> >>> https://download.opensuse.org/tumbleweed/iso/ >>> >>> Best Regards. >>> >>> --- >>> ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp >>> ┃＼／彡 >>> ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the >>> Secure Future Initiative, to incorporate key security features >>> into its core set of technology platforms and cloud services. " >>> >>> -- Microsoft overhauls cyber strategy to finally embrace security by default -- >> That link is incorrect date, use this one < >> https://download.opensuse.org/tumbleweed/iso/Changes.20241217.txt >> -Seasons Hopes🫥 > > the link is ok. it lets one choose the date while your's is *only* for > 20241217 :) > Ok thanks, -Seasons Best

1 0

Blocking PackageKit:
by -pj 20 Dec '24

20 Dec '24

Hi, situation: Block Packagekit from running: Do you want PackageKit to never run? # systemctl stop --now packagekit \ && zypper refresh \ && zypper remove --clean-deps PackageKit \ && zypper addlock --comment 'Packagekit was hung, blocking zypper. BYE!' PackageKit The command above fails with the following displayed < Invalid unit name " " escaped as "\x20" (maybe you should use systemd-escape?). Robert Webb provided the mentioned solution above (previously). I am looking the mailing up again right now. The mailing list page was not working. -Regards

4 20

3 pairs of xeyes?
by bent fender 19 Dec '24

19 Dec '24

I have a line in ~/.profile that calls a script which in turn includes: if [ "$desktop" = "kde" ] then echo "it is kde" xeyes -geometry 70x50+36+420 & xeyes -geometry 70x50+1750+420 & else echo "No kde, no xeyes" fi Which 'used to' give me 2 pairs of xeyes nestled between the two deskbar panels on the sides. Lately however I've ben getting 3 of them: https://imgur.com/2M5Zbil.png In this image (made to brag about my not usb but SATA desktop external bay) you can see my monitor showing the KDE plasma desktop photographed as part of my IKEA pine desktop then reloaded as a desktop wallpaper before that desktop being snapped up to imgur. I 'suspect' SDDM which begins with a lo-res desktop (the two pairs of xeyes on the left) but then they get redrawn as the desktop rolls into high-res with the left one being repeated in the same place as the first time. I have NO CLUE really, just poking around. What gives?

4 56

Test:
by -pj 18 Dec '24

18 Dec '24

This is a test email message.

1 0

Sound setup failure in OpenSuSE 15.6
by Marc Chamberlin 18 Dec '24

18 Dec '24

I have a computer devoted to handling my media center and recently upgraded it from OpenSuSE 15.5.to 15..6 (KDE X-11 Plasma desktop) and now I am having troubles setting up the sound system. Whenever I right click on the small speaker icon in the kicker bar, to configure the audio devices, and select any one of the playback devices and try to test the speakers, I get the following error - Error trying to play a test sound. The system said: "System error" NOT very helpful IMHO! I have followed, and done what I could do, the suggestions outlined at - https://en.opensuse.org/Sound_troubleshooting but many of the steps ran into the above mentioned "System error". I have no idea how to go about debugging the openSuSE sound subsystem, there doesn't seem to be any log files associated with the sound system to study, nor does the general messages log file show anything about sound system failures. The following shows my sound system hardware components - > # inxi -Aa > Audio: > Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio > driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c > class-ID: 0403 > Device-2: Intel 9 Series Family HD Audio vendor: Gigabyte > driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0 > class-ID: 0403 > Device-3: Creative Labs EMU10k2/CA0100/CA0102/CA10200 [Sound Blaster > Audigy Series] driver: snd_emu10k1 v: kernel bus-ID: 03:00.0 > chip-ID: 1102:0004 class-ID: 0401 > Device-4: BEHRINGER GmbH UMC202HD 192k driver: snd-usb-audio type: USB > rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-11:6 > chip-ID: 1397:0507 class-ID: fe01 > Device-5: Texas Instruments PCM2900 Audio Codec > driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s > lanes: 1 mode: 1.1 bus-ID: 3-4:3 chip-ID: 08bb:2900 class-ID: 0300 > API: ALSA v: k6.4.0-150600.23.25-default status: kernel-api with: aoss > type: oss-emulator tools: alsactl,alsamixer,amixer > Server-1: PipeWire v: 1.0.5 status: off with: wireplumber status: active > tools: pw-cat,pw-cli,wpctl > Server-2: PulseAudio v: 17.0 status: active (root, process) > with: pulseaudio-alsa type: plugin tools: pacat,pactl As always, all help and suggestions offered are much appreciated, thank you. Marc

4 20

[oS-en] [OT] Double band WiFi and IoT
by Carlos E. R. 17 Dec '24

17 Dec '24

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have classified the post as OT because it is not about Linux, but the consequences of doing what these IoT tell us to do affect our Linux machines. Excuse possible spelling errors, aspell crashes (locks in black, actually). Long ago I got a router that has the 2.4 Ghz band and the new 5 Ghzx band. The ISP had it configured with two similar but different SSID. Here someone recomended to change to the same SSID and leave it to automatics to choose which band to use. He was right, laptops and phones are happy. Then a few months ago I had installed a remote controller for a water heating system for a house, from Daunier Duval. The technician, when setting up the internet connection for the device, which is done from the phone app, not from a setup menu on the gadget, said that the double band WiFi I had was not compatible, that I had to separate them. OR, we can use the guest band, that typically is separate. We did that and it worked. Yesterday I was setting up a weather station (<https://www.amazon.co.uk/gp/product/B0DDTG79J2/>). The setting up is done in the phone. You have to download an app, register, and follow the instructions. When it reached the WiFi part, it complained that the phone was on the 5 Ghz band, and the gadget is 2.4 only. The instructions warned that double band is not compatible, and that possibly I'd have to separate the bands. I sat there, puzzled, for a while. I thought about setting up the guest band. But at the end, I told the app to continue, it asked for the SSID password, and the thing worked just fine. Bullet avoided, this time. Why are these IoT gadgets telling us to separate the 2.4 and 5 Ghz bands? What does it matter to them that there is also an SSID with the same name in another band, that the actual gadget can not even see because it is on 5 GHz, and they do not have hardware to receive that band? It is only the app on the phone setup tool which can see the double band and complain. Obviously, sepparating these bands is a bad thing for our (Linux) laptops. But if this happens to you, you have two posibilities: ignore the warning and try, and if it fails, setup the guest WiFi with separate SSIDs or even with no 5Ghz band. - -- Cheers Carlos E. R. (from 15.5 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZ2Cn2xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVvT8An02mUR5b4jvEdIHR34uJ Ln5/26aEAJ4+WKeIIEVNdcl62zLYq8PuXFgrQg== =002d -----END PGP SIGNATURE-----

6 15

Bluetooth and sound system connection not working
by Marc Chamberlin 15 Dec '24

15 Dec '24

I have another issue that appears to be in the realm of the sound system, this time on my laptop. I am running OpenSuSE 15.6 with the KDE/Plasma desktop. I recently acquired a set of Bluetooth hearing aids and thought, wouldn't it be nice to be able to connect them to my laptop, so that I could listen to AudioBooks or music, without disturbing my wife while working on the laptop. After a bit of head scratching, cursing, etc I got the Bluetooth connection between my hearing aids and the laptop working. (At least according the the Bluetooth widget in the kicker bar) Trouble is, there is no device for my hearing aids showing up in the list of devices my sound system knows about. I installed pavucontrol to see if it saw anything related to a Bluetooth connection to my hearing aids in it's list of output devices, but no it doesn't, only shows my laptop's "Raptor Lake-P/U/H cAVS Pro" sound devices. So no joy getting sound directed to my hearing aids. From my internet searches I found a few suggestions saying don't use the Pulseaudio drivers with Bluetooth devices, but instead use the Pipewire drivers, so I have switched my laptop over to using Pipewire but still no joy. I checked the kernel messages for errors but nothing significant showed up there - > #dmesg | grep Bluetooth [ 6.616455] Bluetooth: Core ver 2.22 [ > 6.616478] Bluetooth: HCI device and connection manager initialized > [ 6.616482] Bluetooth: HCI socket layer initialized [ 6.616484] > Bluetooth: L2CAP socket layer initialized [ 6.616485] Bluetooth: > SCO socket layer initialized [ 6.746371] Bluetooth: hci0: Device > revision is 0 [ 6.746383] Bluetooth: hci0: Secure boot is enabled [ > 6.746388] Bluetooth: hci0: OTP lock is enabled [ 6.746392] > Bluetooth: hci0: API lock is enabled [ 6.746396] Bluetooth: hci0: > Debug lock is disabled [ 6.746404] Bluetooth: hci0: Minimum > firmware build 1 week 10 2014 [ 6.746405] Bluetooth: hci0: > Bootloader timestamp 2019.40 buildtype 1 build 38 [ 6.747644] > Bluetooth: hci0: DSM reset method type: 0x00 [ 6.785281] Bluetooth: > hci0: Found device firmware: intel/ibt-0040-0041.sfi [ 6.785291] > Bluetooth: hci0: Boot Address: 0x100800 [ 6.785292] Bluetooth: > hci0: Firmware Version: 91-33.24 [ 8.264829] Bluetooth: hci0: > Waiting for firmware download to complete [ 8.265480] Bluetooth: > hci0: Firmware loaded in 1445503 usecs [ 8.265546] Bluetooth: hci0: > Waiting for device to boot [ 8.282317] Bluetooth: hci0: Device > booted in 16413 usecs [ 8.282318] Bluetooth: hci0: Malformed MSFT > vendor event: 0x02 [ 8.286451] Bluetooth: hci0: Found Intel DDC > parameters: intel/ibt-0040-0041.ddc [ 8.288321] Bluetooth: hci0: > Applying Intel DDC parameters completed [ 8.291344] Bluetooth: > hci0: Firmware timestamp 2024.33 buildtype 1 build 81755 [ > 94.927759] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ > 94.927762] Bluetooth: BNEP filters: protocol multicast [ > 94.927765] Bluetooth: BNEP socket layer initialized [ 94.928631] > Bluetooth: MGMT ver 1.22 [ 125.869741] Bluetooth: RFCOMM TTY layer > initialized [ 125.869749] Bluetooth: RFCOMM socket layer initialized > [ 125.869753] Bluetooth: RFCOMM ver 1.11 My internet research says that the one anomaly showing up - Malformed MSFT vendor event: 0x02 is nothing to worry about. It is caused by a driver not clearing a normal event signal and wrongfully putting it on a stack where higher layers in the sound subsystem don't know what to do with it. There is a patch and write-ups about it at https://github.com/bluez/bluez/issues/877 https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.gi… I have installed the following packages, as suggested by my internet research - bluez bluez-auto-enable-devices (and all dependent packages) pipewire pipewire-pulseaudio (and all dependent packages) I read the wiki at https://en.opensuse.org/Bluetooth but found it unhelpful. I suspect it's rather out of date. (seems to talk about stuff that does not apply or exist on my system) Does anyone have any ideas on why my Bluetooth hearing aids are not showing up as sound output capable devices? Got me stumped and as always my gratitude and thanks for helping me solve this little problem... Marc..

2 2