February 2023 - openSUSE Users - openSUSE Mailing Lists

[oS-EN] M$ has a cross-platform PowerShell
by Carlos E. R. 07 Feb '23

07 Feb '23

Can be installed on Windows, Linux, and macOS. <https://learn.microsoft.com/en-us/powershell/scripting/overview?view=powers…> Interesting move. Can be used over ssh. -- Cheers / Saludos, Carlos E. R. (from Telcontar, using openSUSE Leap 15.4)

5 5

missing font ??
by Michael Spartana 06 Feb '23

06 Feb '23

HI, ok well I'm getting this error when starting xemacs Missing charsets in String to Fontset conversion google shows many errors of this variety and either a missing font or an xlib error..... so I was hoping someone here would know..... mike

2 4

transmission quits
by Albert Oszkó 04 Feb '23

04 Feb '23

Hi all, I use Transmission to handle torrent files (in KDE, TW). Today I had a big "zypper dup", nearly 500 items were downloaded. After restart Transmission unexpectedly quits after a few seconds. Ktorrent is dead, I cannot even import an existing torrent file into it. I tried it also in Xfce, with the same result. Interestingly, in IceWM Transmission does not exit. Please help me identify the reason . I saw during dup some files were removed. So I uninstalled and reinstalled Transmission, without any positive result. Thanks for your help, Albert

2 2

[oS-EN] [rant] Wasting time.
by Carlos E. R. 04 Feb '23

04 Feb '23

Hi, as is my routine for years, but today on a secondary computer (alternate location), I open a folder of documents in "mc", select the february.odt file, hit enter, and start editing. Damn! They have changed how to position photos, no anchor to page. Must be a new Libre Office Writer version. After wasting a quarter of an hour fighting how the thing thinks it should place the images, instead of simply obeying me, I decide to ask here. What version am I using... go to help, look about... it is Abiword! Why the heck is 'mc' opening a LO file with Abiword when LO is installed? I look in 'mc', do not find .odt in the extension file... so unininstall Abiword. Get out of my way. But now on open the document it Maximizes to the entire display, and refuses to unmaximize and resize. I can do so with Calc, but not with Writer. The word "resize" is greyed out even after "unmaximize". How the heck can I unmaximize the document? I can not work this way! Ok, go to XFCE settings, change the theme to some other one, and now it works again. But a while later, I open another document with Write, and again it is stuck on maximize, and theme change does not work this time. A new manner occurs to me. Click and hold on the tittle bar and drag down... and it is gone. I can not find the window. I right-click on the "thing" on the display panel, and manage to tell it to move to an empty workspace. Now I see the window: 2 mm wide, 30 mm high rectangle. WTF!? After fiddling with it for a minute or two, I manage to resize it to something sensible and move back to my workspace. Has my computer being possessed by some ghost? -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.4)

4 4

I cursor
by Marc Chamberlin 04 Feb '23

04 Feb '23

Hi, I am running OpenSuSE 15.3 and 15.4 with the KDE/Plasma desktop. My eyes are not as good as they once were, and one of the things that bugs me a lot is the I bar cursor (also called the I beam cursor I think) Is there any way to get rid of it and substitute the regular arrow cursor for it? I don't see the I cursor very well and am constantly losing track of it, requiring lots of mouse movements before I find it again. Marc...

6 7

sound issue (was: Dropping yast2-sound)
by Per Jessen 03 Feb '23

03 Feb '23

Carlos E. R. wrote: > On 2023-01-26 19:31, Patrick Shanahan wrote: >>> >>>> Many people have been doing that, uninstall-reinstall for years and >>>> years. >>> >>> Can't say I'm one of them. >> >> but you have heard of many people uninstall/reinstall as a solutin? Not exactly, but maybe I'm not moving in the right circles :-) Overall, I don't subscribe to such band-aid "solutions", especially not when it ought to be easy to diagnose the problem. (sound is hardly black magic any more). > Google it. That presumes I am interested :-) > Examples: > ><https://www.gamedev.net/forums/topic/339562-sound-only-works-after-restarti…> SuSE 9.3, from 2005 ... almost twenty years old. Seriously? ><https://unix.stackexchange.com/questions/165696/restarting-all-sound-servic…> openSUSE 12.3 - 8 years old? Instead of trawling through the archives of time, maybe post some config data and some dmesg output (related to your sound module). -- Per Jessen, Zürich (-0.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

18 88

CIFS and sym links
by Roger Oberholtzer 03 Feb '23

03 Feb '23

If I create a link on a Windows NTFS disk (on Windows via mklink /d), that link shows up correctly on Linux when the disk is mounted via CIFS. For example: l--------- 1 rst root 0 Feb 2 10:41 ProgramFiles -> Program Files I can follow the link as expected. That's nice. However, if try to create a sym link on Linux (ln -s) on that CIFS volume, I get: ln: failed to create symbolic link 'qq': Operation not supported Is it truly not supported? Or is it some option I need to learn about that enables this? I have not checked how a Linux disk mounted in Windows acts in this respect. That's a later exploration. -- Roger Oberholtzer

3 2

Tumbleweed: after reinstall of system: creation of connection KVM fails with error message.
by Stakanov 02 Feb '23

02 Feb '23

particularity: I have the /var/lib/libvirt installed on a RAID 1 on separate hardware. entropy@linux:~> lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 119,2G 0 disk └─md126 9:126 0 119,2G 0 raid1 └─md126p1 259:0 0 119G 0 part /boot/efi sdb 8:16 0 119,2G 0 disk └─md126 9:126 0 119,2G 0 raid1 └─md126p1 259:0 0 119G 0 part /boot/efi sdc 8:32 0 3,6T 0 disk └─sdc1 8:33 0 3,6T 0 part └─md0 9:0 0 3,6T 0 raid1 /var/lib/libvirt sdd 8:48 0 7,3T 0 disk └─sdd1 8:49 0 7,3T 0 part └─md1 9:1 0 7,3T 0 raid1 └─md1p1 259:1 0 7,3T 0 part /home sde 8:64 0 7,3T 0 disk └─sde1 8:65 0 7,3T 0 part └─md1 9:1 0 7,3T 0 raid1 └─md1p1 259:1 0 7,3T 0 part /home sdf 8:80 0 232,9G 0 disk └─sdf1 8:81 0 232,9G 0 part └─md127 9:127 0 232,9G 0 raid1 /var /usr/local /root /srv /boot/grub2/x86_64-efi /boot/grub2/i386-pc /opt / sdg 8:96 0 3,6T 0 disk └─sdg1 8:97 0 3,6T 0 part └─md0 9:0 0 3,6T 0 raid1 /var/lib/libvirt sdh 8:112 1 0B 0 disk sdi 8:128 1 0B 0 disk sdj 8:144 1 0B 0 disk sdk 8:160 1 0B 0 disk sr0 11:0 1 1024M 0 rom normally I did not have any problem in setting up a new system after a reinstall. But now I get: Socket creation for '/var/run/libvirt/virtqemud-sock' failed: No such file or directory Libvirt URI is: qemu:///system Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/connection.py", line 925, in _do_open self._backend.open(cb, data) File "/usr/share/virt-manager/virtinst/connection.py", line 171, in open conn = libvirt.openAuth(self._open_uri, File "/usr/lib64/python3.10/site-packages/libvirt.py", line 147, in openAuth raise libvirtError('virConnectOpenAuth() failed') libvirt.libvirtError: Socket creation for '/var/run/libvirt/virtqemud-sock' failed: No such file or directory I am puzzled. Has there been a change in directories of KVM, between var and run? What do I have to do to recover my images that are currently in /var/lib/ libvirt?

3 7

Mesa in packman repos
by Stakanov 02 Feb '23

02 Feb '23

Stupid question of today: why is there a MESA version in the packman repos if opensuse provides one too? To be clear I am talking about the Tumbleweed repos. I recall some graphic card reason, but it is a recall that comes remotely and long time ago. So since this recently caused me some trouble because of shifting repo here and there I wanted to understand. Someone can maybe educate me on this. I do not think that patent rights can be an issue here. Thank you in advance. P.S. this is a re-invoice of the very message. The first vanished, maybe you should check that spamfilter recognize your registered members?

3 3

tw pxe install - usessh no longer works?
by Per Jessen 02 Feb '23

02 Feb '23

After upgrading my TW test system last night, it failed to mount the root filesystem. This morning I wanted to start up the TW installer to investigate. It didn't work, the network wasn't properly initiated - I stumbled over this in the kernel messages, see paste. https://paste.opensuse.org/pastes/93a4c6fe0cb2 "Unknown kernel command line parameters ..." ?? I am booting this: http://download.opensuse.org/tumbleweed/repo/oss/boot/x86_64/loader/linux http://download.opensuse.org/tumbleweed/repo/oss/boot/x86_64/loader/initrd with this PXE setup : label tw64 kernel install/tumbleweed.64bit.kernel append initrd=install/tumbleweed.64bit.initrd usessh=1 sshpassword=1234 noresume net.ifnames=0 install=http://opensuse.herrliberg/tumbleweed/repo/oss (the append line folded, but should be seen as a single line). This was worked for ages and ages (approx). -- Per Jessen, Zürich (5.1°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

2 6